rampstackco/claude-skills-seo / skills/content-strategy
content-strategy
VerifiedDevelop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align content production with broader brand and SEO goals. Triggers on content strategy, content plan, editorial strategy, content pillars, content calendar, editorial calendar, topical authority, topic clusters, content governance, content roadmap, content production. Also triggers when the user is about to start producing content without a strategic plan.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.3 KB |
| references/content-strategy-template.md | markdown | 6.6 KB |
| references/editorial-calendar-template.md | markdown | 7.7 KB |
references/content-strategy-template.md
View on GitHub# Content Strategy: [Brand or Site Name]
**Version:** [X.Y]
**Last updated:** [YYYY-MM-DD]
**Owner:** [Editorial lead]
**Review cadence:** [Quarterly / Annually]
---
## Editorial positioning
### Mission
[One sentence. Why this content program exists.]
### Audience
**Primary:**
[Specific audience segment with the depth of detail your discovery work earned.]
**Secondary:**
[Additional segments, if any.]
**Anti-personas:**
[Who this content is NOT for.]
### Promise
[What readers get from us that they cannot get elsewhere. One paragraph.]
### Distinction
We help [audience] [achieve outcome] by publishing [content type] that [unique angle], unlike [common alternatives] that [common shortcoming].
---
## Content pillars
### Pillar 1: [Pillar name]
- **Theme:** [One sentence]
- **Why we own it:**
- Audience need: [Specific need]
- Brand authority: [Why we're credible]
- Competitive opportunity: [Why this is winnable]
- **Sub-topics** (5 to 15):
- [Sub-topic]
- [Sub-topic]
- [Sub-topic]
- **Cornerstone content** (the 1 to 2 pieces that anchor this pillar):
- [Title or working title]
- [Title or working title]
- **Supporting content** (article types that link back to cornerstone):
- [Type and quantity, e.g., "5 deep-dive articles per quarter"]
### Pillar 2: [Pillar name]
[Same structure]
### Pillar 3: [Pillar name]
[Same structure]
[Continue for all pillars; aim for 3 to 5]
---
## Formats
The program returns to these formats consistently.
### Format 1: [Name, e.g., "In-depth guides"]
- **Description:** [What it is]
- **Length:** [Word count or duration range]
- **Cadence:** [How often we produce one]
- **Use case:** [When this format wins]
### Format 2: [Name]
[Same structure]
### Format 3: [Name]
[Same structure]
[Continue for all formats; aim for 3 to 5]
---
## Editorial calendar structure
### Cadence
**Frequency:** [N pieces per week/month]
**Reasoning:** [Why this cadence; what it can sustainably support]
### Pillar rotation
[How pillars rotate through the calendar. Example: 4 pillars, weekly publishing, each pillar gets one piece per month.]
### Format mix
[Within a typical month, what's the format breakdown?]
Example:
- 2 articles
- 1 case study or interview
- 1 longer guide or data study
- Plus: 1 newsletter (ongoing, separate cadence)
### Flex slots
[How much of the calendar is reserved for timely content, news jacking, or campaign launches?]
Typical: 70% planned, 20% flex, 10% updates to existing content.
### Updates and refreshes
[Plan for refreshing top-performing content. Typically every 6 to 12 months for evergreen pillars.]
---
## Governance
### Roles
| Role | Owner | Responsibility |
|---|---|---|
| Editorial lead | [Name] | Strategy, calendar, quality bar |
| Writer (in-house or freelance) | [Name(s) or agency] | Drafts |
| Subject matter expert | [Name(s)] | Expertise, accuracy review |
| Editor | [Name] | Polish, voice consistency, fact-check |
| SEO lead | [Name] | Keyword optimization, internal linking, schema |
| Publisher | [Name] | CMS publication, scheduling, distribution |
### Production workflow
```
Idea → Brief → Outline → Draft → Edit → Review → Publish → Measure → Update or Retire
```
| Stage | Owner | Inputs | Outputs | Quality bar | Time estimate |
|---|---|---|---|---|---|
| Idea | | | | | |
| Brief | | | | | |
| Outline | | | | | |
| Draft | | | | | |
| Edit | | | | | |
| Review | | | | | |
| Publish | | | | | |
| Measure | | | | | |
| Update or retire | | | | | |
### Quality bar
Every piece of published content meets these standards:
- [ ] Aligned with a defined content pillar
- [ ] Targets a specific audience need
- [ ] Voice and tone consistent with brand standards
- [ ] Factually accurate (sources cited where appropriate)
- [ ] SEO basics handled (title, meta, headers, internal links)
- [ ] Schema applied for the content type
- [ ] Edited by someone other than the writer
- [ ] Reviewed by the editorial lead
### Lifecycle rules
- **Update trigger:** A top-performing evergreen piece reviewed when [trigger, e.g., "stats are 12 months old" or "competitive landscape shifts"]
- **Retire trigger:** A piece is retired (deleted, redirected, or merged) when [trigger, e.g., "no traffic for 12 months and no backlinks"]
- **See also:** `seo-content-audit` for the keep/update/merge/redirect/delete framework
---
## Measurement plan
### Primary metrics
| Metric | Target | Reporting cadence |
|---|---|---|
| Organic traffic | | Monthly |
| Email subscribers | | Monthly |
| Conversions from content | | Monthly |
| [Custom metric] | | |
### Secondary metrics (signals)
- Engaged sessions (sessions over 60 seconds)
- Scroll depth on long-form content
- Internal click-through from articles to commercial pages
- Backlinks earned per piece
- Time on page distribution
- Returning reader rate
### Review cadence
- **Weekly:** Calendar status check
- **Monthly:** Performance metrics review, calendar adjustments
- **Quarterly:** Strategy review, pillar performance, capacity check
- **Annually:** Full strategy refresh, audience research re-validation
---
## Production capacity and budget
### Capacity
- Writers: [number, FTE or freelance, hours per week]
- Editors: [number, hours per week]
- Subject matter experts: [availability]
- Designers/illustrators (if needed): [availability]
### Budget
- Internal labor: [budget]
- Freelance writers: [per piece or per month]
- Subject matter expert honoraria (if external): [per piece]
- Imagery, illustration, video: [per piece or monthly]
- Tools and platforms: [monthly]
### Output capacity at this budget
[Realistic monthly output given the budget. Better to plan conservatively and exceed it than over-promise and under-deliver.]
---
## Distribution
Content does not earn its audience by being published. List the distribution channels and the standard process for promoting each piece.
### Channels
- Owned: site, email, social profiles
- Earned: PR, partnerships, expert mentions
- Paid (if budget): boosted social, sponsored newsletter slots
### Per-piece distribution checklist
When a new piece publishes:
- [ ] Posted to social channels with [N] variations
- [ ] Included in next newsletter
- [ ] Sent to relevant internal stakeholders for sharing
- [ ] Outreach to [N] external mentions or backlink targets
- [ ] Submitted to relevant communities (forums, niche aggregators)
- [ ] Internal link added from [related cornerstone content]
---
## Open questions
[Things that still need to be decided before this strategy is fully operational.]
- [ ] [Question]
- [ ] [Question]
---
## Version history
| Version | Date | Changes |
|---|---|---|
| 1.0 | YYYY-MM-DD | Initial strategy |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |