A/Bテストや実験の設計・実装を支援するスキル。 「A/Bテストを設計して」「スプリットテストしたい」「仮説を立ててテストしたい」「バリアントを比較」等のリクエストで発動。 トラッキング実装は analytics-tracking を参照。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
コンテンツ戦略の立案、トピック選定、記事テーマ決めを行うスキル。「コンテンツ戦略を立てて」「何を書けばいい?」「ブログのテーマを考えて」等のリクエストで発動。For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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 .claude/product-marketing-context.md exists, 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 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.
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."
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 |
When creating a content strategy, provide:
For each recommended piece:
Visual or structured representation of how content interconnects.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
A/Bテストや実験の設計・実装を支援するスキル。 「A/Bテストを設計して」「スプリットテストしたい」「仮説を立ててテストしたい」「バリアントを比較」等のリクエストで発動。 トラッキング実装は analytics-tracking を参照。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
マルチエージェントシステムのアーキテクチャ設計ツールキット。 「エージェントを設計して」「マルチエージェント構成」「エージェントのアーキテクチャ」「オーケストレーション設計」等のリクエストで発動。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ai-agent-campのローカル環境セットアップを確認するスキル。 「セットアップ確認」「環境チェック」「初期設定できてる?」「インストール確認」「依存関係チェック」等のリクエストで発動。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ai-agent-campのスラッシュコマンドをCodexでルーティングするスキル。 「/start-0-1を実行」「スラッシュコマンドを使いたい」「コマンドルーティング」「Cursorのコマンドを使いたい」等のリクエストで発動。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ai-agent-campの環境変数・認証情報を安全に管理するスキル。 「APIキーを設定」「.envを管理」「環境変数の設定」「credential managerを使いたい」「秘密情報の管理」等のリクエストで発動。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ai-agent-campリポジトリの案内・オリエンテーションスキル。 「リポジトリ案内」「次のレッスンは?」「どこから始める」「ツールの違い」「aiagent概要」等のリクエストで発動。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.