Content
67%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 SWOT workflow with specific output counts and a well-sequenced process, but roughly a third of the content pads rather than teaches: the Metadata section duplicates the frontmatter, the quadrant bullet lists restate factors Claude already knows, and the Notes are generic. Trimming those and adding a compact example output would materially tighten it.
Suggestions
Remove the "Metadata" section — it duplicates the name, description, and triggers already present in the YAML frontmatter.
Trim the four quadrant bullet lists (28 bullets of generic factors such as "Brand recognition or reputation") down to only non-obvious or domain-specific factors, or move them to a reference file — Claude can generate standard SWOT factors unaided.
Add a brief worked example or output template (e.g., a condensed sample SWOT with one strength, cross-reference insight, and recommendation) to make the expected deliverable format concrete, and cut Notes lines that restate common knowledge.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The "Metadata" section duplicates the frontmatter, the 28 quadrant bullets ("Brand recognition or reputation", "Resource constraints (budget, team size, skills)") enumerate factors Claude already knows, and "Notes" states the obvious ("SWOT is internal to external assessment"). Multiple padded sections keep it below anchor 4, while the genuinely useful Output Process and Strategic Applications keep it above anchor 2. | 3 / 5 |
Actionability | Concrete, executable guidance throughout: "Identify 5-7 strengths", "Develop 3-5 strategic recommendations", "Prioritize actions and owners", "Identify metrics to track progress", plus specific cross-reference questions. For an instruction-only skill this meets anchor 4; not 5 because there is no worked example or output template showing the expected format. | 4 / 5 |
Workflow Clarity | The "Output Process" is a clearly sequenced numbered 1-8 workflow, with step 5's cross-reference questions ("How do we leverage strengths to capture opportunities?") acting as a synthesis checkpoint. Fits anchor 4 (clear sequence, most checkpoints present); not 5 because there is no explicit validation or output-review step, though no destructive/batch operation exists to trigger the cap. | 4 / 5 |
Progressive Disclosure | Well-organized sections with clear headers and no external references, none of which are strictly needed. Fits anchor 4 (good structure, minor organization gaps): the redundant Metadata section and the generic inlined factor lists are minor placement gaps, and at ~92 lines it does not qualify for the under-50-line simple-skill exception to score 5. | 4 / 5 |
Total | 15 / 20 Passed |