内容选题与发布规划

标识: content-strategy最新版本: 2.1.3安装 7 次更新于 2026-11-06
内容创作搜索研究

围绕受众问题、搜索需求和业务目标规划主题簇、内容优先级与发布日历。

在超级AI助理对话中安装/skill install content-strategy

技能介绍

技能简介

围绕受众问题、业务目标和搜索需求规划内容方向,整理主题、内容优先级与发布节奏,适合建立持续产出的内容计划,而不是只列零散标题。

适用场景

品牌内容规划;SEO 主题策划;季度选题;内容日历;现有内容盘点。

使用方法
  1. 说明业务、目标用户和本期内容目标,并提供现有内容及可用资源。
  2. 补充渠道、时间周期、制作能力和重点产品;有搜索数据或竞品资料时一并提供。
  3. 审阅主题与优先级,选定可执行范围,再细化每个选题的角度、形式和发布日期。
参数与输入说明

可直接用自然语言说明这些选项;带代码样式的参数按实际工具定义处理。

参数或输入项 填写说明
业务目标 品牌认知、自然流量、线索、转化或用户教育,应明确主目标。
受众与主题 用户角色、常见问题、产品类别及内容覆盖边界。
渠道与资源 官网、公众号、视频等渠道,以及人员、预算和制作能力。
周期与证据 周/月/季度节奏,已有内容表现、关键词及竞品资料。
示例需求

为 AI 设备管理平台规划未来 8 周的内容,面向企业设备管理员,每周 2 篇,兼顾离线排障和采购选型,给出主题、受众问题、形式和发布安排。

交付内容

内容方向、主题与优先级、选题说明及可执行的发布日历。

使用前提与注意事项
  • 没有真实搜索或流量数据时,选题判断会作为假设,不编造搜索量及排名。
  • 计划不等于已完成调研、制作或发布,可用产能和关键依赖应明确。

使用说明

以下为技能最新版本的 SKILL.md 正文,智能体按其中的步骤完成任务。

平台使用说明

使用当前 Agent 已提供的文件、搜索、代码或业务工具完成任务,按实际可用能力选择路径。默认以中文回应,并遵循用户指定的语言和交付格式。

  • 接受用户在会话中提供的资料,或通过宿主已授权的文件工具读取其指定文件。需要检索、联网、数据库或业务账号时,先确认对应工具真实可用;没有连接器时,使用用户提供的文本或导出文件。
  • 文中的斜杠命令是任务示例,直接根据用户的自然语言请求启动同一流程即可;不要依赖 Claude 专属的插件命令或不存在的工具名称。
  • 不把示例中的实体、数字或工具结果当作用户事实,不虚构已读取、已执行、已发送或已发布。数据不足时说明缺项并完成现有资料支持的部分。
  • 如果任务需要计算或运行脚本,先确认代码运行环境及所需库。工具缺失时给出具体缺项;解释方法、生成草稿不等于已经运行计算。业务写入只使用真实存在且已经授权的工具。
  • 当前技能的资源路径均相对于本技能目录。运行脚本时从宿主提供的技能根目录解析绝对路径,用户资料与输出保存在工作目录,不写入技能资源目录。

根据用户的目标市场选择中文或海外渠道。需要竞品、搜索需求或排名证据时使用当前可用搜索;无真实数据时将选题假设与已验证事实分开。产品上下文文件可选,不强制安装其它技能。

Content Strategy

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.

Before Planning

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):

1. Business Context
  • What does the company do?
  • Who is the ideal customer?
  • What's the primary goal for content? (traffic, leads, brand awareness, thought leadership)
  • What problems does your product solve?
2. Customer Research
  • What questions do customers ask before buying?
  • What objections come up in sales calls?
  • What topics appear repeatedly in support tickets?
  • What language do customers use to describe their problems?
3. Current State
  • Do you have existing content? What's working?
  • What resources do you have? (writers, budget, time)
  • What content formats can you produce? (written, video, audio)
4. Competitive Landscape
  • Who are your main competitors?
  • What content gaps exist in your market?

Treat Content Like a Product

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.

Searchable vs Shareable

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.

When Writing Searchable Content

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.

  • Target a specific keyword or question
  • Match search intent exactly—answer what the searcher wants
  • Use clear titles that match search queries
  • Structure with headings that mirror search patterns
  • Place keywords in title, headings, first paragraph, URL
  • Provide comprehensive coverage (don't leave questions unanswered)
  • Include data, examples, and links to authoritative sources
  • Optimize for AI/LLM discovery: clear positioning, structured content, brand consistency across the web
When Writing Shareable Content
  • Lead with a novel insight, original data, or counterintuitive take
  • Challenge conventional wisdom with well-reasoned arguments
  • Tell stories that make people feel something
  • Create content people want to share to look smart or help others
  • Connect to current trends or emerging problems
  • Share vulnerable, honest experiences others can learn from

Content Types

Searchable Content Types

Use-Case Content
Formula: [persona] + [use-case]. Targets long-tail keywords.

  • "Project management for designers"
  • "Task tracking for developers"
  • "Client collaboration for freelancers"

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.

  • Target searches like "marketing plan template"
  • Provide immediate standalone value
  • Show how product enhances the template
Shareable Content Types

Thought Leadership

  • Articulate concepts everyone feels but hasn't named
  • Challenge conventional wisdom with evidence
  • Share vulnerable, honest experiences

Data-Driven Content

  • Product data analysis (anonymized insights)
  • Public data analysis (uncover patterns)
  • Original research (run experiments, share results)

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."

Link-Earning Formats

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.

For programmatic content at scale, see programmatic-seo skill.


Content Pillars and Topic Clusters

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.

How to Identify Pillars
  1. Product-led: What problems does your product solve?
  2. Audience-led: What does your ICP need to learn?
  3. Search-led: What topics have volume in your space?
  4. Competitor-led: What are competitors ranking for?
Pillar Structure
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
Pillar Criteria

Good pillars should:

  • Align with your product/service
  • Match what your audience cares about
  • Have search volume and/or social interest
  • Be broad enough for many subtopics

Keyword Research by Buyer Stage

Map topics to the buyer's journey using proven keyword modifiers:

Awareness Stage

Modifiers: "what is," "how to," "guide to," "introduction to"

Example: If customers ask about project management basics:

  • "What is Agile Project Management"
  • "Guide to Sprint Planning"
  • "How to Run a Standup Meeting"
Consideration Stage

Modifiers: "best," "top," "vs," "alternatives," "comparison"

Example: If customers evaluate multiple tools:

  • "Best Project Management Tools for Remote Teams"
  • "Asana vs Trello vs Monday"
  • "Basecamp Alternatives"
Decision Stage

Modifiers: "pricing," "reviews," "demo," "trial," "buy"

Example: If pricing comes up in sales calls:

  • "Project Management Tool Pricing Comparison"
  • "How to Choose the Right Plan"
  • "[Product] Reviews"
Implementation Stage

Modifiers: "templates," "examples," "tutorial," "how to use," "setup"

Example: If support tickets show implementation struggles:

  • "Project Template Library"
  • "Step-by-Step Setup Tutorial"
  • "How to Use [Feature]"

Content Ideation Sources

1. Keyword Data

If user provides keyword exports (Ahrefs, SEMrush, GSC), analyze for:

  • Topic clusters (group related keywords)
  • Buyer stage (awareness/consideration/decision/implementation)
  • Search intent (informational, commercial, transactional)
  • Quick wins (low competition + decent volume + high relevance)
  • Content gaps (keywords competitors rank for that you don't)

Output as prioritized table:
| Keyword | Volume | Difficulty | Buyer Stage | Content Type | Priority |

2. Call Transcripts

If user provides sales or customer call transcripts, extract:

  • Questions asked → FAQ content or blog posts
  • Pain points → problems in their own words
  • Objections → content to address proactively
  • Language patterns → exact phrases to use (voice of customer)
  • Competitor mentions → what they compared you to

Output content ideas with supporting quotes.

3. Survey Responses

If user provides survey data, mine for:

  • Open-ended responses (topics and language)
  • Common themes (30%+ mention = high priority)
  • Resource requests (what they wish existed)
  • Content preferences (formats they want)
4. Forum Research

Use web search to find content ideas:

Reddit: site:reddit.com [topic]

  • Top posts in relevant subreddits
  • Questions and frustrations in comments
  • Upvoted answers (validates what resonates)

Quora: site:quora.com [topic]

  • Most-followed questions
  • Highly upvoted answers

Other: Indie Hackers, Hacker News, Product Hunt, industry Slack/Discord

Extract: FAQs, misconceptions, debates, problems being solved, terminology used.

5. Competitor Analysis

Use web search to analyze competitor content:

Find their content: site:competitor.com/blog

Analyze:

  • Top-performing posts (comments, shares)
  • Topics covered repeatedly
  • Gaps they haven't covered
  • Case studies (customer problems, use cases, results)
  • Content structure (pillars, categories, formats)

Identify opportunities:

  • Topics you can cover better
  • Angles they're missing
  • Outdated content to improve on
6. Sales and Support Input

Extract from customer-facing teams:

  • Common objections
  • Repeated questions
  • Support ticket patterns
  • Success stories
  • Feature requests and underlying problems

Prioritizing Content Ideas

Score each idea on four factors:

1. Customer Impact (40%)
  • How frequently did this topic come up in research?
  • What percentage of customers face this challenge?
  • How emotionally charged was this pain point?
  • What's the potential LTV of customers with this need?
2. Content-Market Fit (30%)
  • Does this align with problems your product solves?
  • Can you offer unique insights from customer research?
  • Do you have customer stories to support this?
  • Will this naturally lead to product interest?
3. Search Potential (20%)
  • What's the monthly search volume?
  • How competitive is this topic?
  • Are there related long-tail opportunities?
  • Is search interest growing or declining?
4. Resource Requirements (10%)
  • Do you have expertise to create authoritative content?
  • What additional research is needed?
  • What assets (graphics, data, examples) will you need?
Scoring Template
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.


Calendar Split: 60/30/10

Balance the editorial calendar so search compounds while shareable pieces keep you visible:

  • 60% searchable — the foundation. Demand you can capture predictably (use-case content, hub/spoke, how-tos).
  • 30% shareable — thought leadership, original data, opinion. Creates demand and earns links/mentions.
  • 10% experimental — new formats, channels, or bets. Cheap insurance against a stale mix.

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.


Per-Format Execution Discipline

Treating content like a product means each format has a production standard, not just a topic:

  • Blog post — write 10 title options before drafting (the title does most of the work; pick the strongest). Plan ~5 editing passes (structure, clarity, evidence, line edit, headline/SEO). For the writing itself, see copywriting.
  • Long-form guide — the flagship of a pillar. Comprehensive enough to be the resource; structured with a table of contents and internal links to spokes. Build the hub before the spokes.
  • Video — script the hook first; front-load the payoff. Repurpose into short-form clips at creation time (see social).
  • Podcast — one interview yields a transcript, quote graphics, short clips, and a written recap. Design the episode knowing it will be atomized.
  • Email — one idea per send; the subject line is the title—write several and pick. For sequences and lifecycle, see emails.

Create Once, Distribute Twice

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:

  • Borrowed (other people's audiences: podcasts, guest posts, partnerships) — discovery / breakthrough reach.
  • Rented (social platforms, ad networks) — engagement, but you don't own the audience or the algorithm.
  • Owned (email list, blog, community) — conversion and the only durable asset. Everything upstream should funnel here.

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:

  • Spray-and-pray — posting everywhere with no flagship and no repurposing plan. Effort scatters, nothing compounds.
  • Platform dependency — building on rented land. Facebook organic reach fell from ~20% to under 2%; any rented channel can throttle you overnight.
  • The ownership paradox — teams spend ~90% of effort on channels they don't control (rented/borrowed) and neglect the owned assets that actually convert and can't be taken away.

For the full distribution spine—the Content Distribution Flywheel, platform half-lives, and the atomization checklist—see the reference below.


Output Format

When creating a content strategy, provide:

1. Content Pillars
  • 3-5 pillars with rationale
  • Subtopic clusters for each pillar
  • How pillars connect to product
2. Priority Topics

For each recommended piece:

  • Topic/title
  • Searchable, shareable, or both
  • Content type (use-case, hub/spoke, thought leadership, etc.)
  • Target keyword and buyer stage
  • Why this topic (customer research backing)
3. Topic Cluster Map

Visual or structured representation of how content interconnects.


Task-Specific Questions

  1. What patterns emerge from your last 10 customer conversations?
  2. What questions keep coming up in sales calls?
  3. Where are competitors' content efforts falling short?
  4. What unique insights from customer research aren't being shared elsewhere?
  5. Which existing content drives the most conversions, and why?

References

  • Content Distribution Spine: Create Once Distribute Twice, ORB as a funnel, the ownership paradox, platform half-lives, the Content Distribution Flywheel, and the per-flagship atomization checklist
  • Headless CMS Guide: CMS selection, content modeling for marketing, editorial workflows, platform comparison (Sanity, Contentful, Strapi)

  • copywriting: For writing individual content pieces
  • seo-audit: For technical SEO and on-page optimization
  • ai-seo: For optimizing content for AI search engines and getting cited by LLMs
  • programmatic-seo: For scaled content generation
  • site-architecture: For page hierarchy, navigation design, and URL structure
  • emails: For email-based content
  • social: For social media content, content atomization, and repurposing execution
  • launch: For the ORB channel-type playbook and launch-day distribution

版本记录

版本发布日期更新说明
2.1.32026-10-20-

相关技能

全部技能 →
论文写作助手 图标

论文写作助手

内容创作、搜索研究

辅助生成论文大纲、文献综述框架和摘要,支持引用格式转换、格式规范检查和答辩准备。

哔哩哔哩工具箱 图标

哔哩哔哩工具箱

内容创作、搜索研究

提供哔哩哔哩热门趋势监测、视频下载与播放、字幕下载和视频发布等功能。

网站 SEO 体检 图标

网站 SEO 体检

内容创作、搜索研究

检查抓取索引、标题、内链、页面速度、多语言和内容质量,输出有依据的修复优先级。

PPT 生成与编辑 图标

PPT 生成与编辑

办公效率、内容创作

创建、读取和编辑 PowerPoint 演示文稿,支持内容提取、幻灯片合并与拆分,以及模板、布局、演讲备注和批注处理。

百度搜索 图标

百度搜索

搜索研究

使用百度 AI 搜索引擎检索网页,获取实时信息、文档和研究资料。

把团队的做事方法沉淀为技能

在技能中心导入技能包、从平台资源生成或在线编写,发布后安装到超级AI助理使用。

前往技能中心
©2025 极简未来
粤ICP备2023060400号
网信算备440307657151501250017号
购买咨询