AB build-docs-creator
Produces a complete, standardized build-documentation package for developers from a project's accumulated design work — a product overview (BRD-style), requirements spec (SRS-style), technical design doc (DD-style), and interface source code with a reference guide, all zipped together. Use when the user asks to 'create build docs,' 'generate the doc package,' 'turn this project into docs for devs,' 'produce an SRS/BRD/DD package,' or wants a developer handoff covering both what to build and why. Works from a Claude Project's conversation history and artifacts (including Claude Design/HTML interfaces), and can incorporate partial docs brought in from elsewhere (e.g. ChatGPT-authored requirements) alongside the project's own content. Do NOT use for a single narrow doc request — this skill's default output is the full package. Not for ongoing SDLC docs (test plans, runbooks, sprint artifacts) — pre-build documentation only.
Produces a complete, standardized build-documentation package for developers from a project's accumulated design work — a product overview (BRD-style)…
As a process B 71/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
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: 7. 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 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 38 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2395 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
- +3Description length 934: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 12 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.