Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, well-structured skill with strong actionability and clear workflow sequencing including validation. Its main weaknesses are moderate verbosity—the 'When to use' and 'Core principles' sections add little value beyond what Claude can infer—and the inability to verify that referenced rule files actually exist in the bundle. The troubleshooting section is a nice touch but could be more concise.
Suggestions
Remove or significantly trim the 'When to use' section since this information is already captured in the skill's description/frontmatter and Claude doesn't need it repeated.
Condense the 'Core principles' section—these are largely self-evident best practices that Claude would follow naturally; consider removing or folding key points into the rule files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary padding. The 'When to use' section repeats what the frontmatter description already covers, and the 'Core principles' section states things Claude would naturally infer (e.g., 'prefer named profiles and explicit output paths'). The troubleshooting section is somewhat verbose for common-sense items. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready CLI commands for both quick start and project-based workflows. The commands are specific (npx snipgrapher render, init) with concrete flags and output paths, plus a verification step. | 3 / 3 |
Workflow Clarity | The quick start shows a clear single-step path, the project workflow is sequenced (init → render → verify), and there's an explicit validation checkpoint (ls -lh to confirm output). The troubleshooting section provides a feedback loop for common failure modes with specific remediation steps. | 3 / 3 |
Progressive Disclosure | The skill references two rule files (setup-and-configuration.md, rendering-workflows.md) with clear one-level-deep navigation, which is good structure. However, no bundle files were provided, so we cannot confirm these references actually exist. The inline troubleshooting section could arguably be in a separate file, and the 'Core principles' and 'When to use' sections add bulk that dilutes the overview quality. | 2 / 3 |
Total | 10 / 12 Passed |