CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

1.79x
Quality

62%

Does it follow best practices?

Impact

86%

1.79x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./config/claude/skills/content-strategy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a comprehensive content strategy guide that covers the topic thoroughly but suffers from significant verbosity—it explains many concepts Claude already understands (buyer stages, keyword research basics, what shareable content is). The frameworks and templates are useful but the skill would benefit greatly from being condensed to its unique, non-obvious insights and having detailed reference material split into bundle files. The workflow could be tightened with explicit sequencing and validation steps.

Suggestions

Cut the skill by 50-60% by removing explanations of concepts Claude already knows (buyer stages, what searchable/shareable content means, basic keyword research) and keeping only the specific frameworks, templates, and non-obvious guidance.

Add an explicit numbered workflow (e.g., '1. Read context → 2. Gather missing info → 3. Research → 4. Prioritize → 5. Validate against business goals → 6. Output strategy') with a validation checkpoint before delivering final recommendations.

Move detailed sections (content ideation sources, buyer stage keyword modifiers, prioritization scoring) into separate bundle files and reference them from SKILL.md as one-level-deep links.

Add a concrete example of a complete output (even abbreviated) showing what a finished content strategy deliverable looks like, rather than just describing the output format abstractly.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~300+ lines, with significant content Claude already knows (what searchable vs shareable content is, how to do keyword research, what buyer stages are, how to analyze competitor content). Much of this is general marketing knowledge that doesn't need to be spelled out in such detail. The prioritization scoring framework, content ideation sources, and buyer stage keyword modifiers are all standard marketing concepts explained at length.

1 / 3

Actionability

The skill provides structured frameworks (scoring templates, pillar structures, keyword modifier lists) and some concrete examples, but lacks executable code or commands. The guidance is specific enough to follow (e.g., search query patterns like 'site:reddit.com [topic]') but much of it remains at the level of frameworks and checklists rather than copy-paste-ready outputs. The output format section helps but is still somewhat abstract.

2 / 3

Workflow Clarity

There's a logical flow from gathering context → research → ideation → prioritization → output, but it's not explicitly sequenced as a numbered workflow. The 'Before Planning' section establishes a starting point, but there are no validation checkpoints or feedback loops. For a strategy task that could produce poor recommendations, there's no step to validate recommendations against business goals or customer data before finalizing.

2 / 3

Progressive Disclosure

The skill references related skills at the bottom (copywriting, seo-audit, programmatic-seo) which is good, but there are no bundle files to offload the extensive detail into. The content ideation sources section, buyer stage keyword research, and prioritization framework could each be separate reference files. As a standalone SKILL.md, it's too monolithic—much of the detailed content (e.g., all 6 ideation sources) should be in supporting files.

2 / 3

Total

7

/

12

Passed

Description

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-structured skill description with strong trigger terms, clear 'when to use' guidance, and excellent boundary-setting with related skills. Its main weakness is that the 'what it does' portion is somewhat general—it could benefit from listing more specific concrete actions like building editorial calendars, creating topic clusters, or performing content gap analysis.

Suggestions

Add more specific concrete actions to the 'what' portion, e.g., 'Builds editorial calendars, creates topic cluster maps, identifies content gaps, and prioritizes content opportunities.'

DimensionReasoningScore

Specificity

The description names the domain (content strategy/planning) and mentions some actions like 'plan a content strategy,' 'decide what content to create,' and 'figure out what topics to cover,' but these are somewhat general and don't list multiple concrete, specific actions like 'build topic clusters, create editorial calendars, analyze content gaps.'

2 / 3

Completeness

Clearly answers both 'what' (plan content strategy, decide what content to create, figure out topics) and 'when' (explicit 'Use when' triggers plus boundary-setting references to related skills like copywriting and 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 highly natural phrases a user would actually use.

3 / 3

Distinctiveness Conflict Risk

Explicitly distinguishes itself from related skills ('For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit'), which creates clear boundaries and reduces conflict risk significantly.

3 / 3

Total

11

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
freekmurze/dotfiles
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.