CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 strong, action-dense body with concrete tools (search operators, a worked scoring model, explicit gates) and well-structured one-level-deep references. The main cost is length: a duplicated hierarchy diagram and motivational prose could be cut without losing guidance, and the overall workflow order is left implicit.

Suggestions

Cut one of the two hub/spoke tree diagrams (the ASCII tree under 'Hub and Spoke' and the 'Pillar Structure' tree show the same hierarchy) and keep the pillared version only, referencing it from the earlier section.

Compress the 'Treat Content Like a Product' framing to one or two lines (the 'brand surface area' idea plus a pointer to the Create Once, Distribute Twice section) instead of a multi-paragraph motivational passage.

Add a brief ordered overview of the end-to-end process at the top (context -> ideation -> prioritization -> calendar -> production -> distribution) so the section sequence is explicit rather than inferred.

DimensionReasoningScore

Conciseness

Mostly efficient, but there is real tightening to do: the hub/spoke hierarchy is drawn twice (the '/topic (hub) |── /topic/subtopic-1' tree and the nearly identical 'Pillar Topic (Hub) |── Subtopic Cluster' tree), and the 'Treat Content Like a Product' section spends roughly ten lines on motivational framing ('brand surface area... working 24/7') that could be one line. Matches anchor 3; anchor 4 would require only minor trims.

3 / 5

Actionability

Highly concrete and executable throughout for an instruction-only skill: exact search operators ('site:reddit.com [topic]', 'site:competitor.com/blog'), buyer-stage keyword modifiers, a weighted scoring template with correctly computed worked totals (8*0.4+9*0.3+7*0.2+6*0.1 = 8.0), the 60/30/10 calendar split, per-format production standards (10 title options, ~5 editing passes), and a defined output format. Matches anchor 5.

5 / 5

Workflow Clarity

A logical, implicitly sequenced flow (context gathering -> ideation -> prioritization -> calendar -> production -> distribution -> output) with explicit checkpoints ('Check for product marketing context first'; the information-gain gate: 'If you can't write that sentence, don't write the piece'). Not a 5 because the end-to-end process order is implicit in section arrangement rather than stated, and there is no error-recovery/feedback loop; comfortably above anchor 3 since checkpoints are present and explicit.

4 / 5

Progressive Disclosure

Both bundle references exist, are exactly one level deep, and are clearly signaled in a dedicated References section with content summaries; the body stays at overview altitude and points detail (the full distribution flywheel, atomization checklist, CMS comparison) to them. Sibling-skill pointers (copywriting, seo-audit, link-building, etc.) are clearly labeled. Matches anchor 5.

5 / 5

Total

17

/

20

Passed

Description

95%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 excellent description: comprehensive natural trigger phrases, explicit what/when guidance, and explicit de-confliction against neighboring skills. The only weakness is that the stated capabilities are three phrasings of one core action rather than a fuller enumeration of the skill's distinct sub-capabilities.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ('plan a content strategy, decide what content to create, or figure out what topics to cover'), but these are near-synonymous variants of one core capability rather than a comprehensive list of distinct actions (e.g., pillar identification, keyword mapping, editorial calendars, prioritization). Matches anchor 4 ('several specific actions; minor gaps'), not anchor 5 which requires multiple distinct concrete actions.

4 / 5

Completeness

Explicitly answers both 'what' ('plan a content strategy, decide what content to create, or figure out what topics to cover') and 'when' ('When the user wants to... Also use when the user mentions...') with concrete trigger phrases. Matches anchor 5 exactly; anchor 4 would require a less explicit 'when.'

5 / 5

Trigger Term Quality

Comprehensive coverage of natural user phrases including synonyms and idiomatic variants: 'content strategy,' 'what should I write about,' 'content ideas,' 'blog strategy,' 'topic clusters,' 'editorial calendar,' 'content pillars,' and 'I don't know what to write.' Clear match for anchor 5; no common natural terms are missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (planning what content to produce) with explicit boundary-setting against adjacent skills: 'For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.' Minimal conflict risk; matches anchor 5.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

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.