Repository navigation
v2.1.0: adopt official Splunk agent-skill conventions - #2
Merged
Merged
Conversation
- SKILL.md: metadata.splunk block, Prerequisites/When to Use/routing, Boundaries, Examples, Troubleshooting; agents/openai.yaml for other agents - evals.json (trigger + behaviour evals), references/sources.md, SECURITY.md, SUPPORT.md - Sanitize API-supplied titles, slugs and release names in both scripts (control characters, newlines, length) so listings cannot inject output - Tests for the new metadata, interface file, evals and sanitization Co-Authored-By: Claude Code <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Compared with splunk/splunk-agent-skills and adopted the patterns that fit a small, script-backed skill:
metadata.splunkblock (domain, products, entities, triggers, not-for, outcomes), Prerequisites, When to Use with explicit routing to lifecycle/product skills, Boundaries, Examples, Troubleshooting.agents/openai.yamlinterface file; install vianpx skills add dd-Splunk/splunkbase-skill(verified it discovers the skill).evals.jsonin the official format (4 positive and 3 negative trigger evals, 5 behaviour evals incl. no-URLs-from-memory, no credentials in chat, unknown compatibility, scope).references/sources.md(URLs checked),SECURITY.md,SUPPORT.md(unofficial project).Not adopted:
license/allowed-toolsfrontmatter (no LICENSE chosen yet;allowed-toolsnames are agent-specific), askills/subfolder layout (root layout already works with the installer), and their long advisory-answer protocol (this skill is a lookup, not an advisor).Test plan
.skillarchive containsagents/openai.yaml, excludesevals.json, SECURITY/SUPPORTv2.1.0🤖 Generated with Claude Code