New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Develop a content strategy covering editorial positioning

by rampstackco · MIT license · ★ 901 on GitHub · updated Sep 15

Content strategy cover

Develop 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…

---
name: content-strategy
description: "Develop 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."
category: strategy-and-discovery
catalog_summary: "Editorial strategy, content calendar, topical authority planning"
display_order: 5
---

# Content Strategy

Plan what content to produce, why, when, and how. Stack-agnostic. Works for blogs, knowledge bases, marketing sites, newsletters, and product content surfaces.

This skill is the strategic layer. Tactical execution sits in `content-and-copy`, `landing-page-copy`, and `email-sequences`. SEO-driven content planning sits in `seo-keyword`. This skill stitches those together into a coherent program.

---

## When to use

Overview

Plan what content to produce, why, when, and how. Stack-agnostic. Works for blogs, knowledge bases, marketing sites, newsletters, and product content surfaces.

What you get

  • Editorial positioning
  • Content pillars (3 to 5, each detailed)
  • Calendar (cadence and structure, not the specific items)
  • Governance (roles, workflow, lifecycle)
  • Measurement plan (metrics, review cadence)
  • Production capacity and budget
Manual install (npx, ZIP)
Claude Codenpx skills add rampstackco/claude-skills --skill content-strategy -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/rampstackco/claude-skills/tar.gz/3d4510a94a76 \ | tar -xz -C ~/.claude/skills --strip-components=2 claude-skills-3d4510a94a76/skills/content-strategy
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/fc25f1e5e8ff1bb3f392/content-strategy.zip" -OutFile "$env:TEMP\content-strategy.zip"; Expand-Archive "$env:TEMP\content-strategy.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md10.3 KB
  • references/2 files · 14.3 KB
Read the files here
rampstackco/3d4510a3 files
SKILL.md
Show the full text218 lines

Content Strategy

Plan what content to produce, why, when, and how. Stack-agnostic. Works for blogs, knowledge bases, marketing sites, newsletters, and product content surfaces.

This skill is the strategic layer. Tactical execution sits in content-and-copy, landing-page-copy, and email-sequences. SEO-driven content planning sits in seo-keyword. This skill stitches those together into a coherent program.


When to use

  • Planning a new content program or relaunching an existing one
  • Defining editorial positioning and content pillars
  • Building an editorial calendar
  • Structuring topic clusters and content hubs
  • Establishing content governance (review, approval, lifecycle)
  • Aligning content with broader brand and revenue goals

When NOT to use

  • Writing specific content pieces (use content-and-copy)
  • Writing landing pages or sales copy (use landing-page-copy)
  • Writing email sequences (use email-sequences)
  • Pure keyword research (use seo-keyword, then return here for strategic planning)
  • Auditing existing content for keep/update/delete decisions (use seo-content-audit)

Required inputs

  • Brand positioning and audience (from brand-discovery or creative-brief)
  • Business goals the content needs to serve (traffic, leads, brand authority, retention)
  • Existing content inventory (if any)
  • Keyword research output (from seo-keyword) if SEO-driven
  • Production capacity (writers, budget, cadence)

If brand positioning is unclear, run brand-discovery first. If audience is undefined, do that work before strategy.


The framework: 5 layers

A content strategy has five layers. Skip layers and the program drifts.

1. Editorial positioning

What this content program stands for. The "why we write" statement.

Components:

  • Mission. Why this content exists. One sentence.
  • Audience. Who it serves. Specific.
  • Promise. What readers get from us they cannot get elsewhere.
  • Distinction. What makes this content different from the 50 other publications in the same space.

Example structure:

We help [audience] [achieve outcome] by publishing [content type] that [unique angle], unlike [common alternatives] that [common shortcoming].

A strong editorial positioning forces choices. If you cannot complete the sentence, the positioning is too vague.

2. Content pillars

The 3 to 5 themes the program owns. Every piece of content belongs to a pillar.

Per pillar, define:

  • Theme. One sentence describing the topic territory.
  • Why we own it. Audience need + brand authority + competitive opportunity.
  • Sub-topics. 5 to 15 sub-topics that fit under the pillar.
  • Cornerstone content. The 1 to 2 pieces that anchor the pillar (long-form, comprehensive, link-worthy).
  • Supporting content. Articles, videos, tools, comparisons that reinforce and link to the cornerstone.

Pillar selection criteria:

  • Audience cares about it (research-backed, not assumed)
  • Brand has credibility or can earn it
  • Topical authority is achievable (you can plausibly become a top-3 source)
  • Connects to revenue (directly or indirectly)
  • Distinguishes you from competitors

3 to 5 pillars is the sweet spot. Fewer than 3 risks brittleness. More than 5 dilutes focus.

3. Content formats and types

The shapes the content takes.

Format dimensions:

  • Length. Short (under 500 words), medium (500 to 1500), long (1500 to 3000), epic (3000+)
  • Depth. Surface (overview) vs. deep (comprehensive)
  • Type. Article, guide, comparison, listicle, case study, interview, data study, tool, video, podcast, newsletter, social
  • Originality. Aggregation (summarizing existing knowledge) vs. original research (new data or insight)
  • Evergreen vs. timely. Lasting value vs. moment-driven

Format selection criteria:

  • Match the audience's preferred consumption (do they read, watch, listen?)
  • Match the topic (some topics demand depth; others demand brevity)
  • Match production capacity
  • Match distribution channels (LinkedIn favors short; YouTube favors video; SEO favors long evergreen)

A content program typically has 3 to 5 formats it returns to consistently. More than that fragments production and brand recognition.

4. Editorial calendar

When content publishes.

Cadence options:

  • High frequency (3+ pieces per week): builds momentum, requires significant production capacity
  • Medium frequency (1 to 2 per week): sustainable for most teams, builds steady audience
  • Low frequency (1 to 4 per month): each piece must be high-impact; longer production cycles
  • Burst-then-pause (10 pieces in a month, then 3 months off): launches and campaigns

Calendar structure:

  • Pillar rotation. If you have 4 pillars and publish weekly, each pillar gets one piece per month.
  • Content type mix. Within a month, blend types (e.g., 2 articles + 1 case study + 1 video).
  • Timely opportunities. Reserve flex slots for newsjacking, seasonal content, launches.
  • Updates and refreshes. Plan time for updating existing high-performing content.

Common failure: publishing whatever happens to get written. Without a calendar, the program drifts toward the topics easiest to write, not the ones the audience needs most.

5. Governance and lifecycle

How content gets made, reviewed, published, measured, and retired.

Production workflow:

Idea → Brief → Outline → Draft → Edit → Review → Publish → Measure → Update or Retire

Per stage, define:

  • Who owns it
  • What inputs they need
  • What outputs they produce
  • What the quality bar is
  • How long it should take

Roles:

  • Editorial lead. Owns positioning, calendar, quality bar.
  • Writers. Produce drafts. May be in-house, freelance, or AI-assisted.
  • Subject matter experts. Provide expertise, review for accuracy.
  • Editors. Polish, ensure voice consistency, fact-check.
  • SEO lead. Keyword optimization, internal linking, schema.
  • Publishers. Ship the content (CMS, scheduling, distribution).

Lifecycle decisions:

  • Update cadence. Top-performing evergreen content reviewed every 6 to 12 months.
  • Retire criteria. Content that no longer serves the audience or hurts the site (use seo-content-audit).
  • Republishing. Updated content republished as fresh, not buried as an update.

Workflow

  1. Confirm inputs. Brand positioning, audience, business goals, capacity. If any are missing, surface that first.
  2. Draft editorial positioning. Mission, audience, promise, distinction. Stress-test the positioning by trying to complete the "We help X" sentence.
  3. Define content pillars. 3 to 5. Each with a theme, justification, sub-topics, and planned cornerstone content.
  4. Choose formats. 3 to 5 formats the program returns to consistently.
  5. Build the calendar. Cadence, pillar rotation, format mix, flex slots.
  6. Set up governance. Roles, workflow, quality bar, lifecycle rules.
  7. Document. Use the template in references/content-strategy-template.md.
  8. Operationalize. Set up the editorial calendar in whatever tool the team uses (CMS, Notion, Airtable, etc.).

Failure patterns

  • Strategy without capacity. A 3-piece-per-week plan with one part-time writer fails. Match strategy to actual production capacity.
  • Pillars chosen for SEO alone. Pillars must serve the audience and the brand, not just keyword opportunity. SEO is a downstream filter, not the strategy itself.
  • Too many pillars. 7 pillars dilute the brand. The audience cannot remember what you stand for.
  • Calendar without governance. Content gets produced but quality drifts. Without a quality bar, the program loses authority.
  • No update plan. Top-performing content goes stale. Competitors with fresher versions overtake.
  • Vanity metrics. Pageviews and follower counts without conversion tracking. Define what success looks like in business terms.
  • Strategy that lives in a doc. A strategy document that doesn't translate to the editorial calendar and the production workflow is decoration. Operationalize or it doesn't exist.

Output format

Default output is a strategy document at content-strategy.md plus an editorial calendar in whatever tool the team uses.

Strategy document structure:

  1. Editorial positioning
  2. Content pillars (3 to 5, each detailed)
  3. Formats
  4. Calendar (cadence and structure, not the specific items)
  5. Governance (roles, workflow, lifecycle)
  6. Measurement plan (metrics, review cadence)
  7. Production capacity and budget

Editorial calendar (separate, ongoing):

  • One row per planned content piece
  • Columns for: title, pillar, format, target keyword (if SEO-driven), publish date, owner, status

If required data is unavailable

This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.


Reference files

1---
2name: content-strategy
3description: "Develop 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."
4category: strategy-and-discovery
5catalog_summary: "Editorial strategy, content calendar, topical authority planning"
6display_order: 5
7---
8 
9# Content Strategy
10 
11Plan what content to produce, why, when, and how. Stack-agnostic. Works for blogs, knowledge bases, marketing sites, newsletters, and product content surfaces.
12 
13This skill is the strategic layer. Tactical execution sits in `content-and-copy`, `landing-page-copy`, and `email-sequences`. SEO-driven content planning sits in `seo-keyword`. This skill stitches those together into a coherent program.
14 
15---
16 
17## When to use
18 
19- Planning a new content program or relaunching an existing one
20- Defining editorial positioning and content pillars
21- Building an editorial calendar
22- Structuring topic clusters and content hubs
23- Establishing content governance (review, approval, lifecycle)
24- Aligning content with broader brand and revenue goals
25 
26## When NOT to use
27 
28- Writing specific content pieces (use `content-and-copy`)
29- Writing landing pages or sales copy (use `landing-page-copy`)
30- Writing email sequences (use `email-sequences`)
31- Pure keyword research (use `seo-keyword`, then return here for strategic planning)
32- Auditing existing content for keep/update/delete decisions (use `seo-content-audit`)
33 
34---
35 
36## Required inputs
37 
38- Brand positioning and audience (from `brand-discovery` or `creative-brief`)
39- Business goals the content needs to serve (traffic, leads, brand authority, retention)
40- Existing content inventory (if any)
41- Keyword research output (from `seo-keyword`) if SEO-driven
42- Production capacity (writers, budget, cadence)
43 
44If brand positioning is unclear, run `brand-discovery` first. If audience is undefined, do that work before strategy.
45 
46---
47 
48## The framework: 5 layers
49 
50A content strategy has five layers. Skip layers and the program drifts.
51 
52### 1. Editorial positioning
53 
54What this content program stands for. The "why we write" statement.
55 
56**Components:**
57- **Mission.** Why this content exists. One sentence.
58- **Audience.** Who it serves. Specific.
59- **Promise.** What readers get from us they cannot get elsewhere.
60- **Distinction.** What makes this content different from the 50 other publications in the same space.
61 
62**Example structure:**
63 
64> We help [audience] [achieve outcome] by publishing [content type] that [unique angle], unlike [common alternatives] that [common shortcoming].
65 
66A strong editorial positioning forces choices. If you cannot complete the sentence, the positioning is too vague.
67 
68### 2. Content pillars
69 
70The 3 to 5 themes the program owns. Every piece of content belongs to a pillar.
71 
72**Per pillar, define:**
73- **Theme.** One sentence describing the topic territory.
74- **Why we own it.** Audience need + brand authority + competitive opportunity.
75- **Sub-topics.** 5 to 15 sub-topics that fit under the pillar.
76- **Cornerstone content.** The 1 to 2 pieces that anchor the pillar (long-form, comprehensive, link-worthy).
77- **Supporting content.** Articles, videos, tools, comparisons that reinforce and link to the cornerstone.
78 
79**Pillar selection criteria:**
80- Audience cares about it (research-backed, not assumed)
81- Brand has credibility or can earn it
82- Topical authority is achievable (you can plausibly become a top-3 source)
83- Connects to revenue (directly or indirectly)
84- Distinguishes you from competitors
85 
863 to 5 pillars is the sweet spot. Fewer than 3 risks brittleness. More than 5 dilutes focus.
87 
88### 3. Content formats and types
89 
90The shapes the content takes.
91 
92**Format dimensions:**
93 
94- **Length.** Short (under 500 words), medium (500 to 1500), long (1500 to 3000), epic (3000+)
95- **Depth.** Surface (overview) vs. deep (comprehensive)
96- **Type.** Article, guide, comparison, listicle, case study, interview, data study, tool, video, podcast, newsletter, social
97- **Originality.** Aggregation (summarizing existing knowledge) vs. original research (new data or insight)
98- **Evergreen vs. timely.** Lasting value vs. moment-driven
99 
100**Format selection criteria:**
101 
102- Match the audience's preferred consumption (do they read, watch, listen?)
103- Match the topic (some topics demand depth; others demand brevity)
104- Match production capacity
105- Match distribution channels (LinkedIn favors short; YouTube favors video; SEO favors long evergreen)
106 
107A content program typically has 3 to 5 formats it returns to consistently. More than that fragments production and brand recognition.
108 
109### 4. Editorial calendar
110 
111When content publishes.
112 
113**Cadence options:**
114 
115- **High frequency** (3+ pieces per week): builds momentum, requires significant production capacity
116- **Medium frequency** (1 to 2 per week): sustainable for most teams, builds steady audience
117- **Low frequency** (1 to 4 per month): each piece must be high-impact; longer production cycles
118- **Burst-then-pause** (10 pieces in a month, then 3 months off): launches and campaigns
119 
120**Calendar structure:**
121 
122- **Pillar rotation.** If you have 4 pillars and publish weekly, each pillar gets one piece per month.
123- **Content type mix.** Within a month, blend types (e.g., 2 articles + 1 case study + 1 video).
124- **Timely opportunities.** Reserve flex slots for newsjacking, seasonal content, launches.
125- **Updates and refreshes.** Plan time for updating existing high-performing content.
126 
127**Common failure:** publishing whatever happens to get written. Without a calendar, the program drifts toward the topics easiest to write, not the ones the audience needs most.
128 
129### 5. Governance and lifecycle
130 
131How content gets made, reviewed, published, measured, and retired.
132 
133**Production workflow:**
134 
135```
136Idea → Brief → Outline → Draft → Edit → Review → Publish → Measure → Update or Retire
137```
138 
139**Per stage, define:**
140 
141- Who owns it
142- What inputs they need
143- What outputs they produce
144- What the quality bar is
145- How long it should take
146 
147**Roles:**
148 
149- **Editorial lead.** Owns positioning, calendar, quality bar.
150- **Writers.** Produce drafts. May be in-house, freelance, or AI-assisted.
151- **Subject matter experts.** Provide expertise, review for accuracy.
152- **Editors.** Polish, ensure voice consistency, fact-check.
153- **SEO lead.** Keyword optimization, internal linking, schema.
154- **Publishers.** Ship the content (CMS, scheduling, distribution).
155 
156**Lifecycle decisions:**
157 
158- **Update cadence.** Top-performing evergreen content reviewed every 6 to 12 months.
159- **Retire criteria.** Content that no longer serves the audience or hurts the site (use `seo-content-audit`).
160- **Republishing.** Updated content republished as fresh, not buried as an update.
161 
162---
163 
164## Workflow
165 
1661. **Confirm inputs.** Brand positioning, audience, business goals, capacity. If any are missing, surface that first.
1672. **Draft editorial positioning.** Mission, audience, promise, distinction. Stress-test the positioning by trying to complete the "We help X" sentence.
1683. **Define content pillars.** 3 to 5. Each with a theme, justification, sub-topics, and planned cornerstone content.
1694. **Choose formats.** 3 to 5 formats the program returns to consistently.
1705. **Build the calendar.** Cadence, pillar rotation, format mix, flex slots.
1716. **Set up governance.** Roles, workflow, quality bar, lifecycle rules.
1727. **Document.** Use the template in [`references/content-strategy-template.md`](references/content-strategy-template.md).
1738. **Operationalize.** Set up the editorial calendar in whatever tool the team uses (CMS, Notion, Airtable, etc.).
174 
175---
176 
177## Failure patterns
178 
179- **Strategy without capacity.** A 3-piece-per-week plan with one part-time writer fails. Match strategy to actual production capacity.
180- **Pillars chosen for SEO alone.** Pillars must serve the audience and the brand, not just keyword opportunity. SEO is a downstream filter, not the strategy itself.
181- **Too many pillars.** 7 pillars dilute the brand. The audience cannot remember what you stand for.
182- **Calendar without governance.** Content gets produced but quality drifts. Without a quality bar, the program loses authority.
183- **No update plan.** Top-performing content goes stale. Competitors with fresher versions overtake.
184- **Vanity metrics.** Pageviews and follower counts without conversion tracking. Define what success looks like in business terms.
185- **Strategy that lives in a doc.** A strategy document that doesn't translate to the editorial calendar and the production workflow is decoration. Operationalize or it doesn't exist.
186 
187---
188 
189## Output format
190 
191Default output is a strategy document at `content-strategy.md` plus an editorial calendar in whatever tool the team uses.
192 
193Strategy document structure:
1941. Editorial positioning
1952. Content pillars (3 to 5, each detailed)
1963. Formats
1974. Calendar (cadence and structure, not the specific items)
1985. Governance (roles, workflow, lifecycle)
1996. Measurement plan (metrics, review cadence)
2007. Production capacity and budget
201 
202Editorial calendar (separate, ongoing):
203- One row per planned content piece
204- Columns for: title, pillar, format, target keyword (if SEO-driven), publish date, owner, status
205 
206---
207 
208## If required data is unavailable
209 
210This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.
211 
212---
213 
214## Reference files
215 
216- [`references/content-strategy-template.md`](references/content-strategy-template.md) - Strategy document template.
217- [`references/editorial-calendar-template.md`](references/editorial-calendar-template.md) - Spreadsheet column definitions and calendar structure.
218 
View all files on GitHub →

Details

Updated
Sep 15, 2026
License
MIT
Stars on the repo
★ 901
Checked
Source
rampstackco/claude-skills ↗
Creator
rampstackco · 60 listings
View creator

Made with content-strategy

Content strategy — Showcase grid filtered by Tone equals Provocative and Sensory equals Resonant, showing eight matching brand cards with… (from the rampstackco/claude-skills README)
Content strategy — Showcase grid filtered by Tone equals Provocative and Sensory equals Resonant, showing eight matching brand cards with… (from the rampstackco/claude-skills README)

by rampstackco

Content strategy — Showcase grid with all four axis filters set to Provocative, Editorial Restrained, Coach, and Resonant, showing zero… (from the rampstackco/claude-skills README)
Content strategy — Showcase grid with all four axis filters set to Provocative, Editorial Restrained, Coach, and Resonant, showing zero… (from the rampstackco/claude-skills README)

by rampstackco

Content strategy — RampStack architecture diagram. A central navy hub card shows the RampStack mark with the subtitle 'Stack-agnostic… (from the rampstackco/claude-skills README)
Content strategy — RampStack architecture diagram. A central navy hub card shows the RampStack mark with the subtitle 'Stack-agnostic… (from the rampstackco/claude-skills README)

by rampstackco

Similar skills

See all →
SkillA monthly or weekly content calendar01 content calendar globalminhnv0807/ai-business-skills · by minhnv0807Use when the user needs a monthly or weekly content calendar — posting schedule per channel, funnel ratio, content pillars, repurposing matrix, and an owner per slot. Trigger on 'content calendar', 'posting schedule', 'what should we post this month', 'editorial calendar', 'social media plan', 'we post randomly with no plan'. Also use when the user only says the team keeps running out of things to post. Not for — the brief for one specific post, see `36-content-brief-global`; the caption text itself, see `37-social-caption-global`; deciding next period content from last period data, see `40-next-content-plan-global`; a paid campaign timeline, see `02-campaign-brief-global`.★ 599 GitHub starsSkillGenerate a weekly Facebook Page content plan from a themeFacebook Page Content Plannersergebulaev/facebook-skills · by sergebulaevGenerate a weekly Facebook Page content plan from a theme, audience, and content pillars. Produces per-day picks (short post vs story post, hook formula, angle, posting time, primary goal), a short-to-story post mix, a daily comment-reply target, and a share-optimized goal-mix balance check across shares, comments, and reactions. Use when the user wants to plan a week of Page content. Not for drafting one post (use fb-post-writer) or replying to comments (use fb-engagement-drafter).★ 49 GitHub starsPromptCreate a detailed plan to review guides, blog postsComprehensive content review planf/prompts.chat · by Erkam DemirciCreate a detailed plan to review guides, blog posts, and comparison pages for potential issues, verify them, and implement fixes.New listingPromptCreate a detailed studio beauty editorial close-up shotStudio Beauty Editorial (close-up, pro)f/prompts.chat · by DorukCreate a detailed studio beauty editorial close-up shot prompt. The prompt will include specific instructions on subject demographics, pose, setting, camera details, lighting, and mood to achieve a high-end beauty campaign feel. It will also define technical constraints and negative prompts to avoid unwanted elements.New listingMCPCreates comprehensive content outlines and topic clustersSEO content plannerwshobson/agents · by wshobsonCreates comprehensive content outlines and topic clusters for SEO. Plans content calendars and identifies topic gaps. Use PROACTIVELY for content strategy and planning.★ 39.9k GitHub starsMCPBuilds content engines that rank, convert, and compoundContent strategistalirezarezvani/claude-skills · by alirezarezvaniBuilds content engines that rank, convert, and compound. Thinks in systems — topic clusters, not individual posts. Every piece earns its place or gets killed. Use when content needs to behave like a system rather than a stream of posts — e.g., designing a topic-cluster plan to grow organic traffic from zero, or auditing an editorial calendar and killing pieces that don't convert after 90 days. (For single-asset, on-brand copy production, see cs-content-creator.)★ 26.3k GitHub stars

More from rampstackco

SkillRun a comprehensive WCAG accessibility audit coveringrampstackco/claude-skills · by rampstackcoRun a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use this skill whenever the user wants to audit accessibility, review WCAG compliance, fix accessibility issues, prepare for accessibility certification, address an accessibility lawsuit risk, or systematically improve a site's accessibility. Triggers on accessibility audit, WCAG audit, a11y audit, accessibility compliance, ADA compliance, screen reader test, keyboard navigation, accessibility report, fix accessibility, axe scan. Also triggers when accessibility issues have been reported and need systematic remediation.★ 901 GitHub starsSkillOptimize content and site structure for AI-driven searchAEO and GEOrampstackco/claude-skills · by rampstackcoOptimize content and site structure for AI-driven search experiences including AI overviews, large language model citations, generative answer engines, and AI assistants. Use this skill whenever the user wants to optimize for AI search, get cited by language models, appear in AI overviews, build llms.txt, structure content for AI extraction, or future-proof their SEO for the shift from blue links to AI answers. Triggers on AEO, GEO, AI search, AI SEO, AI overview, generative search, LLM optimization, llms.txt, AI citation, ChatGPT search, Perplexity, Gemini, Claude search, AI assistant optimization, answer engine. Also triggers when the user expresses concern about AI eating their organic traffic or wants to understand how to remain visible as search shifts.★ 901 GitHub starsSkillRun a structured after-action review on a launch, incidentAfter action reportrampstackco/claude-skills · by rampstackcoRun a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.★ 901 GitHub starsSkillDesign measurement frameworks including event taxonomyAnalytics strategyrampstackco/claude-skills · by rampstackcoDesign measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement. Triggers on analytics strategy, measurement plan, event taxonomy, tracking plan, KPI framework, dashboard design, north star metric, attribution model, conversion tracking, GA4 setup, Mixpanel setup, analytics audit. Also triggers when the user has data but no clear way to use it, or wants to make decisions but doesn't know what to track.★ 901 GitHub starsSkillDirect visual and creative work for campaigns, photographyArt directionrampstackco/claude-skills · by rampstackcoDirect visual and creative work for campaigns, photography, illustration, video, and branded experiences. Use this skill whenever the user wants to brief a photographer, direct illustrators, plan a creative campaign, develop visual concepts, or evaluate creative work for fit. Triggers on art direction, photo brief, photography brief, illustration brief, campaign concept, creative concept, visual direction, mood board, look and feel, visual treatment, video direction. Also triggers when the user has approved brand identity but needs to extend it into specific creative deliverables. Use `creative-direction` instead when the ask is the project-wide aesthetic brief that this skill consumes as input.★ 901 GitHub starsSkillPlan and run backups, set recovery objectivesBackup and disaster recoveryrampstackco/claude-skills · by rampstackcoPlan and run backups, set recovery objectives, and run disaster recovery drills. Use this skill when defining RPO/RTO targets, designing backup architecture, deciding what to back up and how often, planning for full-region or platform outages, or running a restoration drill. Triggers on backup, restore, RPO, RTO, disaster recovery, DR, business continuity, what if the database is gone, what if our hosting goes down, recovery drill, ransomware planning. Also triggers when an incident reveals a gap in restoration capability.★ 901 GitHub stars