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.

1.79x

Quality

73%

Does it follow best practices?

Impact

86%

1.79x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/content-strategy/SKILL.md

The canonical home for this skill is content-strategy in coreyhaines31/marketingskills

Quality

Content

57%Weight 40%Scale 1-5

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

The content is a well-structured, actionable reference for content strategy with concrete operators, formulas, and a scoring template. Its main weaknesses are verbosity from re-explaining basic SEO concepts, an implicit rather than explicit workflow, and a monolithic single-file structure with no progressive disclosure to separate references.

Suggestions

Trim or remove explanations of basic SEO concepts Claude already knows (e.g., the 'Searchable content captures existing demand' definitions and generic 'use clear titles' bullets) to improve conciseness.

Frame the overall process as an explicit numbered workflow (gather context -> ideate -> prioritize -> produce output) with a validation or self-check step before delivering the strategy.

Consider splitting the long keyword-modifier and ideation-source reference tables into bundled reference files linked from the main SKILL.md to enable progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body re-explains concepts Claude already knows (e.g., 'Searchable content captures existing demand' and basic SEO bullets like 'Use clear titles that match search queries'), and at ~350 lines it could be tightened, though much of it is genuine domain-specific reference material.	3 / 5
Actionability	Provides concrete, copy-paste-ready guidance — search operators like 'site:reddit.com [topic]', formulas like '[persona] + [use-case]', buyer-stage keyword modifiers, and a weighted scoring template — though a few advisory bullets such as 'Tell stories that make people feel something' remain vague.	4 / 5
Workflow Clarity	Section ordering implies a flow (gather context, ideate, prioritize, output) but it is framed as a reference manual rather than an explicit sequenced workflow, and there are no validation checkpoints or feedback loops.	3 / 5
Progressive Disclosure	Well-organized with clear headers and tables, but it is a single ~350-line file with no bundle references or one-level-deep split; the under-50-line simple-skill exception does not apply, and content that could live in separate references is inlined.	3 / 5
	Total	13 / 20 Passed

Description

90%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it explicitly covers both what the skill does and when to use it, lists comprehensive natural trigger terms, and clearly disambiguates from neighboring skills. The only weakness is that the stated actions are abstract planning verbs rather than concrete operations.

Dimension	Reasoning	Score
Specificity	Lists three named actions ('plan a content strategy, decide what content to create, or figure out what topics to cover') but they are abstract planning verbs with overlap rather than concrete granular operations, and they omit the prioritization and keyword work the skill actually performs.	3 / 5
Completeness	Explicitly answers both 'what' (plan/decide/figure out) and 'when' ('When the user wants... Also use when the user mentions...') with concrete trigger phrases, matching the anchor example closely.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases a user would actually say — 'content strategy,' 'what should I write about,' 'content ideas,' 'blog strategy,' 'topic clusters,' 'content planning' — including synonyms and variations.	5 / 5
Distinctiveness Conflict Risk	Clear niche (content strategy planning) with explicit disambiguation pointing to copywriting for individual pieces and seo-audit for SEO audits, minimizing conflict with adjacent skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: TheCraigHewitt/seomachine
Path: .claude/skills/content-strategy/SKILL.md
Commit: e818d5e

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.