content-strategy
When the user needs to plan, prioritize, or structure a content program -- including identifying content pillars, mapping content to the buyer journey, choosing content types, or building an editorial calendar.
83
80%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/content-strategy/SKILL.mdQuality
Discovery
82%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 is a strong description with excellent trigger terms and specificity for content strategy planning. Its main weakness is that it's structured entirely as a 'when' clause without a separate 'what it does' statement, making the capabilities implicit rather than explicit. Adding a brief capability statement before the trigger clause would make it more complete.
Suggestions
Add a leading capability statement before the 'When' clause, e.g., 'Plans and structures content programs, identifies content pillars, maps content to buyer journeys, and builds editorial calendars. Use when...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'plan, prioritize, or structure a content program', 'identifying content pillars', 'mapping content to the buyer journey', 'choosing content types', 'building an editorial calendar'. | 3 / 3 |
Completeness | The description effectively answers 'when' ('When the user needs to...') but the 'what does this do' is only implied through the trigger conditions rather than explicitly stated as capabilities. It reads more as a trigger clause without a clear 'what it does' preamble. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'content program', 'content pillars', 'buyer journey', 'content types', 'editorial calendar', 'prioritize', 'plan'. These are terms a marketing professional would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around content strategy and editorial planning with specific terms like 'content pillars', 'buyer journey', and 'editorial calendar' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable content strategy skill with a clear workflow and concrete scoring frameworks. Its main weakness is length — it packs a lot of general content marketing best practices inline that could either be trimmed (Claude knows much of this) or split into referenced files. The workflow is logically sequenced and the examples effectively illustrate expected outputs.
Suggestions
Move the 'Frameworks & Best Practices' section to a separate reference file (e.g., CONTENT-BEST-PRACTICES.md) and link to it, keeping only the most critical or non-obvious guidelines inline.
Trim general marketing truisms that Claude already knows (e.g., 'A great article with no distribution plan underperforms...', 'Search engines and audiences reward depth') to reduce token usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary elaboration. Sections like 'Frameworks & Best Practices' contain general content marketing wisdom that Claude likely already knows (e.g., 'A great article with no distribution plan underperforms a good article with a strong distribution plan'). Some bullet points could be tightened, but overall it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific scoring weights (Customer impact 40%, Content-market fit 30%, etc.), specific keyword modifiers for buyer journey stages, concrete content type recommendations with clear descriptions, and specific publishing cadence recommendations. The examples show what good output looks like with specific deliverables. | 3 / 3 |
Workflow Clarity | The 8-step workflow is clearly sequenced and logically ordered from gathering context through to distribution planning. Each step has clear sub-components. While content strategy doesn't involve destructive operations requiring validation checkpoints, the workflow includes appropriate decision points (e.g., classifying content need based on stage, scoring and prioritizing before building the calendar). | 3 / 3 |
Progressive Disclosure | The skill references related skills at the bottom (seo-technical, social-content, email-marketing) which is good navigation. However, the content is quite long and monolithic — the Frameworks & Best Practices section and the detailed content type descriptions could potentially be split into referenced files. The inline detail level is high for a single SKILL.md file. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- shawnpang/startup-founder-skills
- Commit
4ad31b4
- 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.