content-strategy

Use when the user wants to plan a content strategy, decide what content to create, figure out topics, or mentions content strategy, content planning, or editorial calendars.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/content-strategy/SKILL.md

Quality

Content

61%Scale 1-5

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

This is a comprehensive content strategy skill that provides useful frameworks, scoring templates, and structured approaches. Its main weakness is verbosity—many sections explain marketing concepts Claude already understands, and the skill could be 40-50% shorter without losing actionable value. The workflow could benefit from an explicit step-by-step process with validation checkpoints rather than presenting sections as reference material.

Suggestions

Add an explicit numbered workflow at the top (e.g., '1. Check product-marketing context → 2. Gather business context → 3. Research and ideate → 4. Prioritize using scoring template → 5. Deliver output format') to improve workflow clarity.

Trim sections that explain general marketing concepts Claude already knows (e.g., what searchable vs shareable content is, how keyword modifiers work) and focus on the specific frameworks and decision criteria unique to this skill.

Consider moving the detailed Content Ideation Sources section (keyword data analysis, call transcript mining, forum research, competitor analysis) into a separate reference file to improve progressive disclosure and reduce the main skill's length.

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~250+ lines) and includes some content Claude would already know (e.g., explaining what searchable vs shareable content means, basic keyword modifier patterns, general content marketing concepts). However, the frameworks and structured templates do add value. Several sections could be significantly tightened—for example, the Content Ideation Sources section extensively describes how to analyze keyword data, call transcripts, and surveys in ways that are fairly obvious to Claude.	3 / 5
Actionability	The skill provides concrete frameworks (scoring templates, pillar structures, keyword modifier lists, output format specifications) and specific examples throughout. However, it lacks executable code or commands—this is appropriate for an instruction-only skill. The guidance is specific enough to act on (e.g., the prioritization scoring template with weights, the buyer stage keyword modifiers), though some sections like 'Forum Research' are more directional than fully actionable.	4 / 5
Workflow Clarity	The skill has a rough sequence (gather context → research → ideate → prioritize → output), but it's not explicitly laid out as a numbered workflow. The 'Before Planning' section establishes a starting point, and the 'Output Format' section defines the end state, but the middle steps are presented as reference sections rather than a clear sequential process. There are no explicit validation checkpoints or feedback loops (e.g., validating strategy against business goals before finalizing).	3 / 5
Progressive Disclosure	The skill references external files appropriately (product-marketing.md context, references/headless-cms.md, related skills like copywriting, seo-audit, programmatic-seo). The structure uses clear section headers and the content is organized logically. However, given the length, some sections (like the full Content Ideation Sources breakdown) could be split into a separate reference file. The references section and related skills section are well-signaled.	4 / 5
	Total	14 / 20 Passed

Description

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

This description is heavily weighted toward 'when' triggers but almost entirely lacks a 'what' component — it never explains what the skill actually does, produces, or how it helps. The trigger terms are decent but could include more synonyms. The description would benefit significantly from adding concrete capabilities before the 'Use when' clause.

Suggestions

Add a 'what' clause before the 'Use when' section describing concrete actions, e.g., 'Creates content strategies, generates topic ideas, builds editorial calendars, and maps content to audience segments.'

Expand trigger terms to include common synonyms like 'content calendar', 'content roadmap', 'blog topics', 'publishing schedule', or 'content ideas'.

Add specificity about outputs or deliverables (e.g., 'produces structured editorial calendars, topic clusters, and content briefs') to distinguish from general marketing or writing skills.

Dimension	Reasoning	Score
Specificity	The description names the domain (content strategy/planning) but lists only vague actions like 'plan a content strategy' and 'decide what content to create' without specifying concrete deliverables or methods. It lacks specifics about what the skill actually produces or does.	2 / 5
Completeness	The 'when' is explicitly and clearly stated with a 'Use when...' clause and multiple trigger scenarios. However, the 'what' is essentially missing — the description never explains what the skill actually does or produces, only when to invoke it.	3 / 5
Trigger Term Quality	Includes several natural trigger terms users would say: 'content strategy', 'content planning', 'editorial calendars', 'topics', 'what content to create'. Missing some synonyms like 'content calendar', 'blog topics', 'content roadmap', 'publishing schedule'.	4 / 5
Distinctiveness Conflict Risk	The focus on content strategy and editorial calendars provides some distinctiveness, but 'content planning' and 'topics' are broad enough to overlap with skills related to SEO, blog writing, social media management, or general marketing strategy.	3 / 5
	Total	12 / 20 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/content-strategy/SKILL.md
Commit: fbdfd63

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