Content
92%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
An exemplary process skill body: exact pinned commands, explicit validation checkpoints and feedback loops at every phase, fail-closed gates, and clean one-level-deep disclosure to real reference and script files. The only flaw is minor repetition of the dependency pins within the install section.
Suggestions
Drop the redundant 'Generation requires exactly:' text block in the install section since the pinned versions already appear in the uv command and the frontmatter compatibility field.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and imperative — hard gates, exact requirements lists, and commands with no filler or explanations of concepts Claude already knows. Minor redundancy keeps it below 5: the install section lists the exact pins twice ('uv pip install "python-pptx==1.0.2"...' followed by a text block repeating the same three pins, which also appear in frontmatter compatibility). | 4 / 5 |
Actionability | Every phase gives copy-paste-ready, exact-pinned commands with flags and output paths (e.g., 'python -B scripts/validate_manifest.py poster.json --print-content-hash', 'python -B scripts/generate_poster.py poster.json --output poster.pptx --report poster.generation.json'), plus explicit post-conditions and failure criteria — fully executable coverage of the common path. | 5 / 5 |
Workflow Clarity | The pipeline is clearly sequenced (install → requirements → manifest → validate → asset/palette audits → generate → package/layout inspection → manual gates → export) with validation commands at each phase, explicit 'Stop instead of guessing' hard gates, and feedback loops ('Any non-approval edit invalidates approval', 'Re-run all checks after any change'). | 5 / 5 |
Progressive Disclosure | The body is an overview that defers detail to well-signaled, one-level-deep references ('Read references/poster_layout_design.md', 'Follow references/manifest_spec.md'), all of which exist on disk, plus a Bundled CLIs section enumerating the scripts. No content that belongs in a separate file is inlined and there is no nested-reference chain. | 5 / 5 |
Total | 19 / 20 Passed |