CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

content-strategy

Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align content production with broader brand and SEO goals. Triggers on content strategy, content plan, editorial strategy, content pillars, content calendar, editorial calendar, topical authority, topic clusters, content governance, content roadmap, content production. Also triggers when the user is about to start producing content without a strategic plan.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A well-crafted strategy skill body: concrete, opinionated guidance with real templates properly split into references and a clear sequenced workflow. The main improvements are removing repetition between the framework sections and Failure patterns, and adding explicit verification checkpoints to the later workflow steps.

Suggestions

Trim restated guidance in Failure patterns that duplicates the framework sections (e.g., pillar-count limits already stated in layer 2), keeping only failure modes not already covered.

Add an explicit verification checkpoint to later workflow steps, e.g., after building the calendar validate it against stated production capacity (the "Strategy without capacity" failure), and re-check the pillar set against the selection criteria before documenting.

Consider moving the detailed format dimensions (length/depth/type/originality lists) into the strategy template reference to tighten the overview further.

DimensionReasoningScore

Conciseness

The body is mostly lean, domain-specific heuristics Claude does not already know (pillar counts, cadence bands, length bands, selection criteria), but framework guidance is restated in the Failure patterns section — e.g., "3 to 5 pillars is the sweet spot… More than 5 dilutes focus" repeats "Too many pillars. 7 pillars dilute the brand." This is anchor 4 (efficient, minor trimming possible) rather than 5 because of that duplicated guidance and a few compactable explanatory sentences.

4 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: a fill-in positioning sentence ("We help [audience] [achieve outcome] by publishing [content type]…"), numeric specifications throughout (3-5 pillars, 5-15 sub-topics, cadence bands, 6-12 month review cycles), an 8-step workflow, a concrete output document structure with calendar columns, and two real templates in references/. Specific examples cover the common cases, matching anchor 5.

5 / 5

Workflow Clarity

The 8-step workflow is clearly sequenced with early checkpoints — step 1 gates on missing inputs ("If any are missing, surface that first") and step 2 includes a positioning stress-test — plus a data-gap protocol and a failure-patterns checklist. It sits at anchor 4 rather than 5 because later steps (calendar, governance, operationalize) lack explicit verification checkpoints or re-validate loops after drafting.

4 / 5

Progressive Disclosure

The body is a well-organized overview and both referenced bundle files (content-strategy-template.md and editorial-calendar-template.md, verified to exist as substantial templates) are one level deep, clearly signaled both in workflow step 7 and in a dedicated Reference files section. Content is appropriately split and navigation is easy, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Description

96%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.

An exemplary description: concrete third-person capabilities, an explicit what-and-when structure, and a rich natural-language trigger list. The only weakness is slight overlap risk on broad terms like "content production" with adjacent tactical content skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning" plus plan/define/build/structure/set up/align — with comprehensive coverage of the domain in third-person voice. It matches anchor 5 rather than 4 because the six named layers leave no gaps in what the skill does.

5 / 5

Completeness

It explicitly answers both what ("Develop a content strategy covering…") and when ("Use this skill whenever the user wants to…", "Triggers on…", plus the no-plan case "when the user is about to start producing content without a strategic plan") with concrete trigger phrases, matching the anchor 5 example structure exactly.

5 / 5

Trigger Term Quality

The trigger list — "content strategy, content plan, editorial strategy, content pillars, content calendar, editorial calendar, topical authority, topic clusters, content governance, content roadmap, content production" — comprehensively covers the natural phrases and synonyms a user would say when they need this skill.

5 / 5

Distinctiveness Conflict Risk

The strategic-planning niche is clear and mostly distinct, but broad triggers like "content production" and "content plan" carry minor overlap risk with closely related tactical writing skills (e.g., copywriting or email-sequence skills) whose users might say the same words. It does not fully match anchor 5's "minimal conflict risk" because the description itself draws no boundary against those adjacent skills.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

rampstackco/claude-skills

Path

skills/content-strategy/SKILL.md

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.