BA document-finder
Scan a directory of documents, classify each file by compliance type, resolve version conflicts with the user, and produce a prioritized analysis plan mapping confirmed-current documents to rote skills.
Scan a directory of documents, classify each file by compliance type, resolve version conflicts with the user, and produce a prioritized analysis plan mapping…
As a process A 80/100 · Runs to the end — weak spots: running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securitySKILL.md:51Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition; documentation table row)| `vulnerability assessment`, `vulnerability scan`, `vulnerability report`, `pen test`, `penetration test`, `penetration testing`, `security assessment`, `security audit`, `security review`, `security
detectortable
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 80/100
- 30Running it twice. 2 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 4 branches
- 70Execution cost. Instruction body is 4934 tokens
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 55 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
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)
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 202: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 55 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.