Content
75%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.
A well-structured, lean instruction skill: concrete connector commands, explicit decision gates, a done-when checklist, and real one-level-deep reference files carrying the templates and worked example. The main improvement space is de-duplicating repeated links/sections, adding an explicit output-verification step, and making the external repo-relative references more self-contained.
Suggestions
Consolidate reference links: remove the duplicate Analysis Templates and Example Report links in 'Reference Materials' (or keep only that section and drop the inline ones) so each file is linked exactly once.
Add an explicit verification step after step 9 (e.g., 'Before delivering, re-check every gap entry names its competitor, its volume/traffic estimate, and its bucket') to close the workflow's validation loop.
Merge the 'Save Results' section with the Skill Contract's memory-promotion bullet to eliminate the repeated hot-cache/research-path guidance, or state the write path once with a pointer.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean — one-line instruction steps, no explanations of concepts Claude already knows, and dense sections like Decision Gates and the quality bar. Minor trimmable redundancy remains: "Save Results" repeats the memory-promotion already stated in Skill Contract, and "Reference Materials" repeats links given inline earlier. Anchor 4 fits: efficient with minor instances that could be trimmed; anchor 5 would require every section to be irreducible. | 4 / 5 |
Actionability | Concrete, executable commands are present (e.g., `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/firecrawl.py" map <competitor-domain> --search "<topic>" --limit 1000`) alongside a concrete "Done when" checklist and sample prompts. The 9 core steps are terse one-line directives whose executable detail is deferred to the referenced templates, which keeps them just short of fully copy-paste-ready. | 4 / 5 |
Workflow Clarity | Nine clearly sequenced steps, explicit stop-and-ask / continue-silently decision gates, a "Done when" checklist, and a Measured/User-provided/Estimated/N/A provenance rule provide strong checkpoints. Not a batch or destructive skill, so no cap applies; an explicit post-draft verification loop is the missing piece versus anchor 5. | 4 / 5 |
Progressive Disclosure | All three referenced bundle files (references/analysis-templates.md, references/gap-analysis-frameworks.md, references/example-report.md) exist, are one level deep, and each carries a clear purpose label; the body works as an overview. Minor gaps: the Reference Materials section duplicates two links already given inline, and several paths (../../../CONNECTORS.md, ../../../references/skill-contract.md, ../../../SECURITY.md, ../../implement/content-writer/SKILL.md) resolve outside this bundle. | 4 / 5 |
Total | 16 / 20 Passed |