← 返回 Skills 市场
mariokarras

Content Strategy

作者 Mario Karras · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ 安全检测通过
284
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install abm-content-strategy
功能描述
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 s...
使用说明 (SKILL.md)

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-context.md exists (or .claude/product-marketing-context.md 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?

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

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

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

Automated content auditing:

Use Firecrawl to crawl and extract content from competitor sites or audit your own:

node tools/clis/firecrawl.js crawl \x3Ccompetitor-blog-url>
node tools/clis/firecrawl.js map \x3Csite-url>

This gives you a structured view of their content architecture, publishing frequency, and topic coverage.

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

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?

Related Skills

  • 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
  • email-sequence: For email-based content
  • social-content: For social media content
安全使用建议
This skill appears coherent and low-risk: it is an instruction-only content-strategy helper that needs no installs or credentials. Two practical things to consider before enabling it for agents that can act autonomously: (1) it will look for and read local product-marketing-context files (.agents/product-marketing-context.md or .claude/product-marketing-context.md) if present — ensure those files do not contain secrets or sensitive internal material you don't want an agent to include in outputs; (2) because the skill produces strategic outputs based on local context, review any content the agent emits before publishing (to avoid accidental disclosure). If you want stricter controls, remove or redact the product-marketing-context files or restrict the skill to manual invocation only.
功能分析
Type: OpenClaw Skill Name: abm-content-strategy Version: 1.0.0 The skill bundle provides a comprehensive framework for content strategy, including keyword research, topic clustering, and competitor analysis. It includes instructions for the agent to read a local context file (.agents/product-marketing-context.md) and suggests using a local utility (firecrawl.js) for legitimate web crawling of competitor sites, which aligns with its stated purpose and shows no signs of malicious intent or data exfiltration.
能力评估
Purpose & Capability
The name/description (content strategy) align with the SKILL.md: it instructs the agent to plan pillars, hub-and-spoke, prioritization frameworks, and to ask business/customer questions. No unrelated binaries, credentials, or installs are requested.
Instruction Scope
The runtime instructions direct the agent to check for and read local files (.agents/product-marketing-context.md or .claude/product-marketing-context.md) and to use that context. That behavior is relevant to the skill's purpose, but those optional file reads are not listed in the manifest's config paths — this is a disclosure/privacy note rather than a functional mismatch.
Install Mechanism
No install spec and no code files; the skill is instruction-only, so nothing will be written or executed on disk by an installer.
Credentials
The skill declares no required environment variables, credentials, or external config. The SKILL.md also does not ask for secrets or unrelated credentials.
Persistence & Privilege
always is false and the skill does not request persistent/privileged settings. The skill can be invoked autonomously by the agent (default), which is normal; there is no evidence it modifies other skills or system settings.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install abm-content-strategy
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /abm-content-strategy 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.0
Initial release of the content strategy skill. - Guides users to plan effective content strategies for traffic, authority, and lead generation. - Provides structured frameworks for gathering business, customer, content, and competitive context. - Explains the difference between searchable and shareable content, with actionable tips for each. - Outlines content types, including hub-and-spoke, use cases, templates, thought leadership, and data-driven formats. - Offers guidance on defining content pillars, mapping topics to buyer stages, and using keyword and customer data for ideation. - Clarifies when to use related skills for SEO audits, copywriting, or social content.
元数据
Slug abm-content-strategy
版本 1.0.0
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 1
常见问题

Content Strategy 是什么?

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 s... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 284 次。

如何安装 Content Strategy?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install abm-content-strategy」即可一键安装,无需额外配置。

Content Strategy 是免费的吗?

是的,Content Strategy 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Content Strategy 支持哪些平台?

Content Strategy 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Content Strategy?

由 Mario Karras(@mariokarras)开发并维护,当前版本 v1.0.0。

💬 留言讨论