Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable with clear, validated workflows and copy-paste commands, but leans monolithic and repeats some alias restatements. Splitting reference material into bundle files and trimming redundancy would improve token efficiency.
Suggestions
Trim repeated alias restatements (e.g. the recurring "# or the long form: ..." notes) since the aliases table already covers them.
Move the 'Writing good facts' and 'Domain vocabulary' sections into reference files (e.g. references/writing-facts.md) and link to them, so the main SKILL.md stays an overview.
Consolidate the duplicate lifecycle/workflow command blocks (start-of-work, track-progress, maintain-accuracy) into a single canonical sequence to reduce repetition.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with command-focused sections, but restates aliases ("# or the long form: ...") and repeats the same lifecycle/workflow patterns across sections; some tightening is possible. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready commands throughout (e.g. "facts add 'users can sign up' --section features/auth --tags draft") with concrete arguments and examples for every operation. | 3 / 3 |
Workflow Clarity | Sequences multi-step agent workflows with explicit validation checkpoints ("facts ll" then "facts check" as the primary feedback loop) and a manual-fact verification procedure, with the lifecycle flow @draft -> @spec -> @implemented made explicit. | 3 / 3 |
Progressive Disclosure | No bundle files exist and the content is a single well-sectioned file, but it is a monolithic ~150-line document; sections like the domain vocabulary and writing-good-facts guidance could be offloaded to reference files. | 2 / 3 |
Total | 10 / 12 Passed |