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," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.

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 well-structured instruction skill: the searchable-vs-shareable decision rule and proactive triggers are concrete and actionable, and detail is appropriately offloaded to the bundled reference and script. The main weaknesses are mild internal redundancy and a workflow that is sequenced implicitly by section order rather than as an explicit ordered procedure with checkpoints.

Suggestions

Merge the Task-Specific Questions section into the Before Planning customer-research checklist (or cut it) — its sales-call and pattern questions duplicate items already listed there.

Frame the planning flow as an explicit numbered procedure (gather context → classify searchable/shareable → prioritize topics → cluster map → produce output) with the tool-output review called out as a validation checkpoint.

Add one compact worked example of a prioritized topic row and a pillar/subtopic snippet so the Output Format sections are concrete rather than purely descriptive.

DimensionReasoningScore

Conciseness

The body is composed of lean bullet lists with no explanations of concepts Claude already knows, but there is redundant overlap: "What questions keep coming up in sales calls?" in Task-Specific Questions duplicates "What objections come up in sales calls?" in Before Planning, and the Output Artifacts table partially restates Output Format. This is anchor 4 (efficient with minor trims possible) rather than anchor 5 (every token earns its place) or anchor 3 (no unnecessary explanations).

4 / 5

Actionability

Guidance is mostly executable: a four-branch decision rule ("if it has no volume but a distribution hook → shareable"), copy-paste-ready script commands, and enumerated table columns ("keyword, volume, difficulty, buyer stage, content type, score"). It falls short of anchor 5 only because "Visual or structured representation of how content interconnects" is vague and no worked example of a prioritized topic or pillar is given.

4 / 5

Workflow Clarity

The sequence is coherent and explicitly cued ("Check for product marketing context first", "Once priority topics exist, group them mechanically") with one verification checkpoint on tool output ("the tool groups lexically; you verify buyer-stage coherence"). Anchor 5 is not met because steps are not framed as an ordered procedure with feedback loops; anchor 3 is too low since checkpoints and sequencing are present.

4 / 5

Progressive Disclosure

Clear overview structure with a well-signaled, verified one-level-deep reference ("Full treatment: references/content-strategy-reference.md") and documented executable use of the bundled script; the searchable-vs-shareable detail is correctly deferred rather than inlined, matching 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.

A strong description: explicit what and when, natural trigger phrases, third-person voice, and explicit boundary guidance to adjacent skills. The only gap is that the capability list covers intent-level actions without naming the concrete deliverables the skill produces.

DimensionReasoningScore

Specificity

Lists several concrete actions ("plan a content strategy, decide what content to create, or figure out what topics to cover") but stops short of the fuller capability set (pillars, calendars, gap analysis, briefs) that would merit a 5. It is well above anchor 3, which expects only 1-2 concrete actions. Third-person voice is used consistently ("the user wants", "the user mentions"), so no voice penalty applies.

4 / 5

Completeness

Explicitly answers both what (planning content strategy, deciding what content to create, figuring out topics) and when (two explicit "use when" clauses with concrete trigger phrases), and adds boundary guidance ("For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit."), which is the anchor-5 pattern.

5 / 5

Trigger Term Quality

Six natural user phrasings are provided, including a full question form ("what should I write about") plus "content strategy," "content ideas," "blog strategy," "topic clusters," and "content planning" — comprehensive natural-term coverage with synonyms, matching anchor 5 rather than anchor 4's "a few natural terms missing."

5 / 5

Distinctiveness Conflict Risk

The niche is clear — deciding what to write versus writing it — and it explicitly disambiguates against the two most confusable adjacent skills (copywriting, seo-audit), giving minimal conflict risk per 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

alirezarezvani/claude-skills

Path

marketing-skill/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.