AD skill-publisher
Create, validate, security-scan, and publish skills to ClawHub. Use when asked to "make a skill", "publish a skill", "create a new skill", "scaffold a skill", "package this as a skill", or any request to build and distribute agent capabilities.
As a process D 39/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-privilegescripts/security-scan.sh:88Privilege escalation / world-writable permissions (code comment; documentation of a security skill)# 6. File permissions - check for setuid/setgid (4xxx, 2xxx) which are dangerous
commentsecurity skill -
low Dangerous commands
cmd-privilegescripts/security-scan.sh:91Privilege escalation / world-writable permissions (code comment; documentation of a security skill)# Only flag setuid (4xxx), setgid (2xxx), or world-writable (xx7)
commentsecurity skill
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 39/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (skill-publisher) differs from the folder (skillpub)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 16 steps
- 100Execution cost. Instruction body is 564 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 244: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (6 code blocks)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.