Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is well-structured with a clear sequenced workflow, explicit validation checkpoints, and clean progressive disclosure to real reference files; its main weakness is moderate verbosity and some redundant or generic sections.
Suggestions
Remove or trim the 'Tips for Success' section, whose items ('Study their failures', 'Monitor regularly') are generic knowledge Claude already has.
Cut the redundant 'When This Must Trigger' section or fold it into the frontmatter triggers to avoid duplicating trigger guidance already present in metadata.
Tighten the marketing-style opening paragraph ('revealing what's working in your market and identifying opportunities to outperform the competition') to a leaner purpose statement.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient but includes a marketing-style intro, a 'When This Must Trigger' section that duplicates frontmatter triggers, and generic 'Tips for Success' advice Claude already knows, so it could be tightened. | 2 / 3 |
Actionability | It provides copy-paste prompt examples, specific data-collection lists (e.g., 'URL, domain age, estimated traffic, domain authority'), and concrete validation checklists — actionable guidance for an instruction skill. | 3 / 3 |
Workflow Clarity | An explicit 8-step sequence (Identify → Gather → Keywords → Content → Backlinks → Technical → GEO → Synthesize) is paired with dedicated input and output validation checklists, matching the score-3 anchor. | 3 / 3 |
Progressive Disclosure | The overview points to four well-signaled, one-level-deep reference files (analysis-templates, battlecard-template, positioning-frameworks, example-report) that exist in ./references/, with clear navigation and descriptions. | 3 / 3 |
Total | 11 / 12 Passed |