AB requirement-analysis-assistant
Turn rough business requests, screenshots, sketches, or existing PRDs into structured requirement artifacts: PRD drafts, clarification questions, prototype outlines, HTML demo pages, visual requirement analysis, functional details, interaction rules, edge cases, priorities, acceptance criteria, and quality checks. Use when users ask to analyze, break down, draft, review, standardize, prototype, or visualize product requirements for publishing, gaming, web campaign, recharge center, user acquisition, SDK, admin configuration, or similar business scenarios. Compatible with Codex and OpenClaw AgentSkills-style SKILL.md loading.
Turn rough business requests, screenshots, sketches, or existing PRDs into structured requirement artifacts: PRD drafts, clarification questions, prototype…
As a process B 79/100 · Nearly there — weak spots: when it triggers, running it twice, progress reporting
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: 10. 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 79/100
- 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
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 5 branches
- 100Tools and files. No external tools needed
- 100Steps. 104 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1840 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +4No input/output examples
- +2Single-language instructions
- +3Description length 632: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 104 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.