content-strategy
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
86
Quality
83%
Does it follow best practices?
Impact
86%
1.79xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description with excellent trigger term coverage and clear differentiation from related skills. The main weakness is that the capability description could be more specific about concrete actions the skill performs (e.g., 'create editorial calendars,' 'build topic clusters,' 'identify content gaps'). The cross-references to related skills are a strong feature that reduces conflict risk.
Suggestions
Add more specific concrete actions like 'create editorial calendars,' 'build topic clusters,' 'identify content gaps,' or 'map content to buyer journey stages' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (content strategy) and mentions some actions like 'plan a content strategy, decide what content to create, figure out what topics to cover' but these are somewhat general and not highly concrete actions like 'create topic clusters' or 'analyze content gaps'. | 2 / 3 |
Completeness | Clearly answers both what (plan content strategy, decide what to create, figure out topics) and when (explicit 'Use when' equivalent with trigger phrases). Also helpfully distinguishes from related skills (copywriting, seo-audit). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'content strategy,' 'what should I write about,' 'content ideas,' 'blog strategy,' 'topic clusters,' 'content planning' - these are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Explicitly differentiates from related skills (copywriting for individual pieces, seo-audit for SEO-specific work) and has distinct trigger terms focused specifically on planning and strategy rather than execution. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
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 strong, actionable content strategy skill with excellent workflow structure and concrete guidance including scoring templates, search patterns, and output formats. The main weakness is length—it's comprehensive to the point of being verbose, and some sections could be extracted to separate files for better progressive disclosure. The content assumes appropriate Claude competence for most concepts but occasionally over-explains.
Suggestions
Extract 'Content Types' and 'Content Ideation Sources' sections into separate reference files (e.g., CONTENT-TYPES.md, IDEATION-SOURCES.md) to reduce main file length
Tighten the 'Searchable vs Shareable' section—Claude understands these concepts; focus on the specific guidance rather than definitions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundant explanations (e.g., explaining what searchable vs shareable means when Claude would understand this). Some sections like 'Content Types' could be tightened, though most content earns its place. | 2 / 3 |
Actionability | Provides highly concrete guidance with specific formulas, templates, scoring matrices, and exact search query patterns (e.g., 'site:reddit.com [topic]'). The output format section gives clear deliverable structures. | 3 / 3 |
Workflow Clarity | Clear sequential workflow: gather context → identify pillars → research keywords → ideate → prioritize → output. The 'Before Planning' section establishes a clear starting point, and the prioritization scoring template provides explicit decision-making criteria. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections and references to related skills at the end. However, this is a long document (~300 lines) that could benefit from splitting detailed sections (like Content Types or Ideation Sources) into separate reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
355d067
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.