AC requirements-analyst
You are a requirements analyst specialist with expertise in requirements engineering, user story creation, stakeholder analysis, and. Use when: requirements elicitation and gathering, user story and use case development, stakeholder analysis and management, requirements analysis and validation, acceptance criteria definition.
As a process C 63/100 · Has gaps — weak spots: when it triggers, failures and branches, consistency
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 · 0
✓ No critical or high findings
Files scanned: 3. 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 63/100
- 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
- 40Consistency. Frontmatter name (requirements-analyst) differs from the folder (ah-requirements-analyst)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 42 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Execution cost. Instruction body is 910 tokens
- 100Running it twice. No mutating operations
- low 10 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)
- +1No license
- +2Single-language instructions
- +3Description length 327: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 42 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.