Content
60%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.
The body delivers a clear, actionable workflow backed by real scripts and a genuine reference file, with decent structure and progressive disclosure. Its main weakness is substantial generic template boilerplate that inflates token usage without adding skill-specific value.
Suggestions
Remove or condense the generic template sections ('When to Use', 'Implementation Details', 'Required Inputs', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling') to skill-specific content, since they currently restate generic guidance Claude already applies.
Delete the 'Key Features' bullet that merely re-quotes the frontmatter description, and the 'See ## Workflow above' placeholder under Implementation Details.
Tighten the Workflow's section-generation step by referencing the specific prompt headings in references/prompt_templates.md (Basic Info, Background, Results, Conclusion) rather than describing them abstractly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Roughly half the body is generic template boilerplate ('When to Use', 'Implementation Details', 'Required Inputs', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling') that restates skill-agnostic guidance and even re-quotes the description in 'Key Features'. This is noticeably padded rather than merely tighten-able, placing it below the 3 anchor. | 2 / 5 |
Actionability | The workflow gives concrete, executable commands (`python scripts/extract_text.py <file_path> extracted_content.txt`, Glob patterns, `Read extracted_content.txt`) and points to real scripts and reference files, with only minor gaps (the LLM section-generation steps remain abstract). It is above the 3 anchor but not fully copy-paste complete like the 5 anchor. | 4 / 5 |
Workflow Clarity | A clear 3-step sequenced workflow with sub-steps and validation/error checkpoints (stderr checks, 'Warning: No text extracted' handling, fallback). This is not a destructive/batch operation so the cap does not apply; it sits above 3 but lacks the tight validate->fix->retry feedback loop of the 5 anchor. | 4 / 5 |
Progressive Disclosure | Detail is appropriately offloaded one level deep to real bundle files (`references/prompt_templates.md`, `scripts/extract_text.py`, `scripts/extract_pdf.py`) which are all present and referenced from the body, with a clear overview. It stays below 5 because of the inline generic boilerplate that adds organizational bulk without navigation value. | 4 / 5 |
Total | 14 / 20 Passed |