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

77%

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 ./config/claude/skills/content-strategy/SKILL.md

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

Quality

Content

65%

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

The content is highly actionable and well-organized for an instruction-only skill, with concrete formulas, search operators, and a weighted prioritization model. Its main weaknesses are conciseness (some restatement and long question lists), missing validation checkpoints in the workflow, and the absence of progressive disclosure through separate reference files.

Suggestions

Tighten conciseness by deduplicating the '/blog vs dedicated hub' guidance (it appears under both Content Types and Content Pillars) and condensing the per-section bullet question lists.

Add an explicit validation/verification checkpoint before the Output Format section (e.g., confirm each priority topic maps to a buyer stage, has a target keyword, and is backed by customer-research evidence).

Extract the detailed keyword/ideation source material and the scoring template into reference files (e.g., references/ideation-sources.md, references/prioritization-template.md) and link to them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is substantive and assumes Claude's competence, but it runs long and restates ideas (the '/blog vs dedicated hub' guidance appears in two sections) and includes extensive bullet question lists that could be trimmed.	2 / 3
Actionability	Highly actionable throughout: concrete formulas ([persona] + [use-case]), buyer-stage keyword modifiers, exact search operators (site:reddit.com [topic]), a weighted scoring rubric with a template table, and a structured output format.	3 / 3
Workflow Clarity	There is a clear top-level sequence (context gathering -> ideation -> prioritization -> output), but no explicit validation or verification checkpoints, and the prioritization-to-output path has no 'verify before finalizing' feedback loop.	2 / 3
Progressive Disclosure	Everything lives in one ~240-line SKILL.md with no bundle files or external references; internal headings are well organized, but detailed reference material (keyword sources, scoring template) that could be split out is inline.	2 / 3
	Total	9 / 12 Passed

Description

90%

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 well-constructed: it states what the skill does, gives natural user-facing trigger phrases, and clearly distinguishes itself from sibling skills. The only soft spot is specificity, where the named actions are slightly more abstract than a granular verb list.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ("plan a content strategy, decide what content to create, or figure out what topics to cover") but they are relatively abstract compared to a multi-action list like 'extract, fill, merge.'	2 / 3
Completeness	Clearly answers both what (plan/decide/figure out topics) and when, with an explicit "Also use when the user mentions..." trigger clause.	3 / 3
Trigger Term Quality	Strong coverage of phrases users would naturally say ("content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning").	3 / 3
Distinctiveness Conflict Risk	Has a clear niche and explicitly disambiguates from adjacent skills ("For writing individual pieces, see copywriting"; "For SEO-specific audits, see seo-audit"), minimizing conflict risk.	3 / 3
	Total	11 / 12 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: freekmurze/dotfiles
Path: config/claude/skills/content-strategy/SKILL.md
Commit: d0073bc

Reviewed: about 10 hours 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.