CC reverse-document
Generate missing design or architecture docs from existing implementation — works backwards from code and prototypes.
Generate missing design or architecture docs from existing implementation — works backwards from code and prototypes.
As a process C 57/100 · Has gaps — References files that are not bundled: templates/design-doc-from-implementation.md, templates/architecture-doc-from-code.md, templates/concept-doc-from-prototype.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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 Broad scope
meta-dynamic-shellSKILL.md:40Shell command executed automatically when the skill loads (Claude Code !`cmd` preamble)!`bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys workflow,system_overrides,automation`
Files scanned: 1. 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") - warning
missing-refreference to a missing file: templates/design-doc-from-implementation.md - warning
missing-refreference to a missing file: templates/architecture-doc-from-code.md - warning
missing-refreference to a missing file: templates/concept-doc-from-prototype.md - note
edit-residuethe text marks something as outdated (lines 103): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 57/100
- 0Tools and files. 3 referenced file(s) missing: templates/design-doc-from-implementation.md, templates/architecture-doc-from-code.md, templates/concept-doc-from-prototype.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Result and completion. Does not say what the result is
- 70When it triggers. States when to use, but not when not to
- 85Steps. 54 steps, 2 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3791 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 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)
- +3Description length 117: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 15 headings
- +3Step-by-step instructions: 54 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.