페이지 변경안을 비교하는 A/B 테스트를 가설 설정부터 결과 해석까지 계획합니다. 필요한 표본 수와 기간, 방문자 배분 및 평가 지표를 정하고, 실험 우선순위와 지속적인 개선을 위한 학습 기록도 정리합니다.
- 제목이나 가입 버튼 비교하기
- 필요한 표본 수와 테스트 기간 추정하기
- 결과와 부정적인 영향 확인하기
고객의 질문, 검색 키워드, 경쟁사의 콘텐츠를 바탕으로 제작할 주제와 우선순위를 정합니다. 핵심 주제, 관련 글 구성도, 편집 일정과 게시 후 배포 계획을 사업 목표와 가용 자원에 맞춰 정리합니다.
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.
실행 점수 미검증
설치 방법 보기content-strategy는 사업 목표와 고객의 관심사를 바탕으로 어떤 콘텐츠를 만들지 정하도록 돕습니다. 고객과의 대화, 설문, 검색 키워드, 경쟁사의 게시물에서 주제를 찾고, 고객에게 미치는 영향, 제품과의 관련성, 검색 가능성, 제작 부담을 기준으로 우선순위를 정합니다. 결과물에는 핵심 주제 3~5개, 우선 제작할 기획, 관련 글의 연결 구조도가 포함될 수 있습니다.
기업 블로그의 주제를 정하기 어렵거나, 글을 더 늘리기 전에 콘텐츠의 방향을 맞추고 싶을 때 유용합니다. 검색으로 발견될 콘텐츠와 공유될 가능성이 높은 콘텐츠의 비중을 검토하고, 제작에 투입할 수 있는 인력과 시간도 고려해 계획합니다. 기사, 영상, 음성 콘텐츠를 다른 형식으로 바꾸는 방법과 게시 후 전달 경로도 정리할 수 있습니다.
개별 콘텐츠 작성, 기술 SEO 점검, 소셜 미디어용 콘텐츠 제작은 관련 스킬의 담당으로 안내되어 있습니다. 검색용 기획에서는 기존 상위 문서가 다루지 않은 내용을 새 글이 무엇으로 보탤지 확인합니다.
이 소개문은 공개된 SKILL.md를 바탕으로 AI(OpenAI Codex)가 작성했습니다. 정확한 사양은 아래 원문을 확인하세요.
AI가 SKILL.md의 내용에서 주의가 필요한 작업과 도입 전제를 확인했습니다. 점수는 실제로 실행한 결과(실행 검증)만으로 매깁니다.
점수에는 넣지 않았습니다. 2026년 10월 24일 기준으로 AI(OpenAI Codex)가 판정했습니다. 참고용이므로 설치 전에 원문도 확인해 주세요.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
You are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
Every piece is its own launch. Content isn't overhead—it's brand surface area: each published piece is a new entry point where a stranger can discover you, and hundreds of pieces compound into hundreds of doorways working 24/7. Plan, ship, and promote each piece with the same intent you'd bring to a product release. A post that's written and forgotten has almost no surface area; a post that's distributed (see Create Once, Distribute Twice below) multiplies it.
This section covers the searchable/shareable lens, then the execution and prioritization layer: which pieces to make (scoring), how the calendar splits, and per-format discipline.
Every piece of content must be searchable, shareable, or both. Prioritize in that order—search traffic is the foundation.
Searchable content captures existing demand. Optimized for people actively looking for answers.
Shareable content creates demand. Spreads ideas and gets people talking.
The information-gain gate: before committing to a searchable piece, read the current top results for its query and write one sentence on what yours will add that none of them have: original data, a real product example, a working tool or template, a clearer answer, a stronger opinion. If you can't write that sentence, don't write the piece. It will be the eleventh copy of the same article, and neither Google nor AI assistants have a reason to prefer it.
Use-Case Content Formula: [persona] + [use-case]. Targets long-tail keywords.
Hub and Spoke Hub = comprehensive overview. Spokes = related subtopics.
/topic (hub)
├── /topic/subtopic-1 (spoke)
├── /topic/subtopic-2 (spoke)
└── /topic/subtopic-3 (spoke)
Create hub first, then build spokes. Interlink strategically.
Note: Most content works fine under /blog. Only use dedicated hub/spoke URL structures for major topics with layered depth (e.g., Atlassian's /agile guide). For typical blog posts, /blog/post-title is sufficient.
Template Libraries High-intent keywords + product adoption.
Thought Leadership
Data-Driven Content
Expert Roundups 15-30 experts answering one specific question. Built-in distribution.
Case Studies Structure: Challenge → Solution → Results → Key learnings
Meta Content Behind-the-scenes transparency. "How We Got Our First $5k MRR," "Why We Chose Debt Over VC."
When the goal of a piece is backlinks specifically, format choice matters more than production effort. Foundation Inc.'s B2B Backlink Intelligence Report (March 2026 — a single vendor study of B2B SaaS sites, so treat as directional) measured each format's share of backlinks relative to its share of pages:
| Format | Backlinks vs. page share |
|---|---|
| Statistics / data roundups | 4.25x |
| Glossary / definition pages | 1.47x |
| Interactive tools / calculators (see free-tools) | 1.38x |
| How-to / tutorials | 1.36x |
| Original research / reports | 0.80x |
| Ultimate guides | 0.77x |
| Thought leadership | 0.74x |
| Templates / frameworks | 0.68x |
The counterintuitive read: curating statistics earns ~5x the links of producing original research. Writers link to whatever makes citation easiest — a maintained stat-roundup page is citation infrastructure, while original research often gets cited via the roundups that aggregate it. Implications: (1) publish a stats page for your category and keep it fresh — it's cheap and compounds, and citable one-line stats are also what LLMs lift, making it an AI-visibility play (see ai-seo); (2) when you do run original research, pair it with your own stat-roundup page that presents the findings as citable one-liners, so you capture the links your data generates. The formats at the bottom aren't dead — guides, templates, and thought leadership earn their keep on rankings, conversions, and brand. Judge each piece by the job it's for, and don't expect links from formats that don't earn them.
To get those assets in front of the people who link, and to point their authority at the pages that need it, see link-building.
For programmatic content at scale, see programmatic-seo skill.
Content pillars are the 3-5 core topics your brand will own. Each pillar spawns a cluster of related content.
Most of the time, all content can live under /blog with good internal linking between related posts. Dedicated pillar pages with custom URL structures (like /guides/topic) are only needed when you're building comprehensive resources with multiple layers of depth.
Pillar Topic (Hub)
├── Subtopic Cluster 1
│ ├── Article A
│ ├── Article B
│ └── Article C
├── Subtopic Cluster 2
│ ├── Article D
│ ├── Article E
│ └── Article F
└── Subtopic Cluster 3
├── Article G
├── Article H
└── Article I
Good pillars should:
Map topics to the buyer's journey using proven keyword modifiers:
Modifiers: "what is," "how to," "guide to," "introduction to"
Example: If customers ask about project management basics:
Modifiers: "best," "top," "vs," "alternatives," "comparison"
Example: If customers evaluate multiple tools:
Modifiers: "pricing," "reviews," "demo," "trial," "buy"
Example: If pricing comes up in sales calls:
Modifiers: "templates," "examples," "tutorial," "how to use," "setup"
Example: If support tickets show implementation struggles:
If user provides keyword exports (Ahrefs, SEMrush, GSC), analyze for:
Output as prioritized table: | Keyword | Volume | Difficulty | Buyer Stage | Content Type | Priority |
If user provides sales or customer call transcripts, extract:
Output content ideas with supporting quotes.
If user provides survey data, mine for:
Use web search to find content ideas:
Reddit: site:reddit.com [topic]
Quora: site:quora.com [topic]
Other: Indie Hackers, Hacker News, Product Hunt, industry Slack/Discord
Extract: FAQs, misconceptions, debates, problems being solved, terminology used.
Use web search to analyze competitor content:
Find their content: site:competitor.com/blog
Analyze:
Identify opportunities:
Extract from customer-facing teams:
Score each idea on four factors:
| Idea | Customer Impact (40%) | Content-Market Fit (30%) | Search Potential (20%) | Resources (10%) | Total |
|---|---|---|---|---|---|
| Topic A | 8 | 9 | 7 | 6 | 8.0 |
| Topic B | 6 | 7 | 9 | 8 | 7.1 |
Score 1-10 per factor, multiply by the weight, sum for the total. Rank the list; make the top-scoring pieces first.
Balance the editorial calendar so search compounds while shareable pieces keep you visible:
This is a starting ratio, not a rule. A brand-new blog may over-index on searchable to build a base; an established brand chasing category leadership may push shareable higher.
Treating content like a product means each format has a production standard, not just a topic:
Creating content is half the job—distribution is the other half, and most teams skip it. The philosophy: one exceptional piece, reformatted and repurposed across every channel, not a fresh piece per platform. Pouring effort into a single flagship and then distributing it everywhere beats spreading thin effort across many mediocre platform-native posts.
Build distribution hooks into the piece at creation time, not after: write subheads that stand alone as social posts, structure sections to be lifted out modularly, and pull quotes/stats you already know you'll graphic-ify. A well-designed guide is a distribution kit in disguise.
The ORB Framework as a funnel — route attention from borrowed → rented → owned, which maps to discovery → engagement → conversion:
ORB mechanics live in the launch skill (channel-type playbook) and content atomization/repurposing lives in social; the value here is consolidating the distribute half of content strategy so it has a home.
Failure modes to avoid:
For the full distribution spine—the Content Distribution Flywheel, platform half-lives, and the atomization checklist—see the reference below.
When creating a content strategy, provide:
For each recommended piece:
Visual or structured representation of how content interconnects.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
페이지 변경안을 비교하는 A/B 테스트를 가설 설정부터 결과 해석까지 계획합니다. 필요한 표본 수와 기간, 방문자 배분 및 평가 지표를 정하고, 실험 우선순위와 지속적인 개선을 위한 학습 기록도 정리합니다.
Google Ads, Meta, LinkedIn, TikTok 등 광고 플랫폼에 맞춰 제목과 본문, 이미지·영상 아이디어를 만듭니다. 실적 데이터와 고객 의견을 활용해 여러 안을 만들고, 형식 제한과 측정 가능한 테스트 기준을 정합니다.
Google Ads, Meta, LinkedIn 등 유료 광고의 매체 선택과 타깃, 예산, 입찰 전략을 정리하고 운영 결과를 검토합니다. 고객 획득 비용과 매출 데이터를 바탕으로 다음 조치를 판단하며 확인된 사실, 가설, 부족한 정보를 구분합니다.
AI 검색 답변에서 브랜드가 어떻게 소개되고 인용되는지 조사하고, 콘텐츠 구성과 근거, 웹사이트 접근 설정을 점검합니다. AI가 주요 정보를 읽을 수 있는지 확인해 개선 방향을 정리합니다.
마케팅 및 제품 개선에 필요한 추적 계획을 세우고 검증합니다. GA4와 Google Tag Manager 설정, 이벤트 누락·중복 확인, UTM 명명 통일, 같은 기간을 기준으로 한 지표 계산을 지원합니다.
App Store와 Google Play 등록 페이지를 여섯 항목으로 점검하고 100점 만점의 종합 점수와 우선순위별 문구·이미지 개선안을 제공합니다. 경쟁 앱과 비교할 수도 있습니다.