AC skill-audit
Runs a deterministic static safety audit for third-party AI skill or plugin repositories before install or execution. Use when asked to scan a skill repo, assess whether a repo is safe to install, run a skill safety assessment, or produce evidence-backed findings for pre-install security screening.
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Risky intent
intent-offensive-securityreferences/prompt-contract.md:33Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Likely exploit chain
-
low Risky intent
intent-offensive-securitySKILL.md:29Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- prompt payload generation through `prompt`
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 34. 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 54/100
- 0Result and completion. Does not say what the result is
- 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. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (skill-audit) differs from the folder (skill-audit-modeio)
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 23 steps
- 100Execution cost. Instruction body is 844 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
- +5Description has no quoted example phrases that should trigger the skill
- +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
- +3Description length 299: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (3 of 4)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.