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," "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.

68

Quality

82%

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

75%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 thorough, actionable strategy skill with concrete frameworks, scoring rubrics, and search operators, structured into navigable sections with a clearly signaled reference file. Its main weakness is redundancy between the Content Types and Content Pillars sections.

Suggestions

Consolidate the hub/spoke and '/blog' guidance into a single location — it is currently restated near-verbatim in both 'Content Types' and 'Content Pillars and Topic Clusters'.

Deduplicate the pillar/hub structural advice (the ASCII tree appears twice) so each section references the shared definition rather than repeating it.

Trim a few list-heavy sections (e.g., overlapping items in 'Content Ideation Sources') to tighten token use without losing the actionable specifics.

DimensionReasoningScore

Conciseness

Mostly efficient and dense with specifics, but the hub/spoke concept and the '/blog' guidance are each restated near-verbatim across separate sections (Content Types vs. Content Pillars), and a few lists could be tightened.

3 / 5

Actionability

Highly actionable for an instruction-only skill: concrete keyword modifiers per buyer stage, a weighted scoring rubric (40/30/20/10) with a template table, content-type formulas, and copy-ready search operators like 'site:reddit.com [topic]'.

5 / 5

Workflow Clarity

A clear sequenced flow runs from gathering context to searchable/shareable decision, content types, pillars, keyword mapping, ideation, prioritization, and an output format, though there are no explicit validation checkpoints.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with one one-level-deep reference clearly signaled in the References section ('Headless CMS Guide' → references/headless-cms.md, verified to exist); minor gaps are the inlined length and a single bundle reference.

4 / 5

Total

16

/

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.

A strong, well-structured description that crisply scopes a planning/strategy niche and packs in natural trigger phrases plus explicit boundaries to adjacent skills. The only soft spot is specificity, where the concrete actions are somewhat overlapping rather than distinct capabilities.

DimensionReasoningScore

Specificity

Names the domain and a few concrete but overlapping actions ('plan a content strategy, decide what content to create, or figure out what topics to cover'), yet coverage is not comprehensive and the actions blur together.

3 / 5

Completeness

Explicitly answers both 'what' ('plan a content strategy, decide what content to create... help deciding what content to produce') and 'when' ('Use when the user wants to... Use this whenever someone needs help deciding what content to produce') with concrete trigger phrases, in third person.

5 / 5

Trigger Term Quality

Comprehensive natural-language triggers users would actually say ('content strategy,' 'what should I write about,' 'content ideas,' 'blog strategy,' 'topic clusters,' 'editorial calendar,' 'I don't know what to write'), including synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Clear niche (deciding what content to produce, not writing it) with explicit disambiguation ('For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.'), minimizing conflict risk.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
coreyhaines31/marketingskills
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.