MCP HubMCP Hub
SKILL·B41D86

content-strategy

rampstackco
업데이트됨 26 days ago
2 조회
953
132
953
GitHub에서 보기
메타design

정보

`content-strategy` 스킬은 개발자가 체계적인 콘텐츠 프로그램을 계획하고, 편집 방향성, 캘린더 및 운영 방침을 정의하도록 지원합니다. 이 스킬은 사용자가 콘텐츠를 SEO 및 브랜드 목표와 맞춰야 할 때나, 계획되지 않은 제작을 시작하기 전에 발동됩니다. 이를 통해 전략적 기반을 마련하며, 실제 실행은 `content-and-copy`와 같은 다른 스킬들이 담당합니다.

빠른 설치

Claude Code

추천
기본
npx skills add rampstackco/claude-skills -a claude-code
플러그인 명령대체
/plugin add https://github.com/rampstackco/claude-skills
Git 클론대체
git clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/content-strategy

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

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

GitHub 저장소

rampstackco/claude-skills
경로: dist/codex/.agents/skills/content-strategy
0
agent-skillsai-agentsanthropicclaudeclaude-aiclaude-code
FAQ

자주 묻는 질문

content-strategy Skill이란 무엇인가요?

content-strategy은(는) rampstackco이(가) 만든 Claude Skill입니다. Skill은 Claude가 필요할 때 불러오는 지침과 리소스를 묶어 추가 프롬프트 없이 content-strategy 관련 작업을 수행할 수 있게 합니다.

content-strategy은(는) 어떻게 설치하나요?

이 페이지의 설치 명령을 사용하세요. content-strategy을(를) Claude Code 플러그인으로 추가하거나 저장소를 skills 디렉터리에 복제한 다음 Claude를 다시 시작해 Skill을 불러옵니다.

content-strategy은(는) 어떤 카테고리에 속하나요?

content-strategy은(는) 메타 카테고리에 속합니다.

content-strategy은(는) 무료로 사용할 수 있나요?

네. content-strategy은(는) AIMCP에 등록되어 있으며 무료로 설치할 수 있습니다.

연관 스킬

content-collections
메타

이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.

스킬 보기
polymarket
메타

이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.

스킬 보기
creating-opencode-plugins
메타

이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.

스킬 보기
sglang
메타

SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.

스킬 보기