Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计提醒

content-strategy内容策略

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

552

周安装

23

GitHub Stars

35

下载量

184
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:content-strategy(内容策略)
来源仓库:https://github.com/superamped/ai-marketing-skills
仓库路径:skills/content-strategy
安装命令:
npx skills add https://github.com/superamped/ai-marketing-skills --skill content-strategy
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/superamped/ai-marketing-skills --skill content-strategy

简介

content-strategy 辅助文档与内容整理,支持 Markdown、README 等格式优化。

  • 适用于提炼结构、统一术语或重组零散材料,提升可读性与一致性。
  • 使用时需保留项目已有事实,避免将未确认信息写成确定结论。
  • 涉及对外文案时应控制语气,防止过度营销或夸大能力描述。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Content Strategy

Usage

Use when building or refreshing a content strategy from scratch, planning content pillars and topic clusters, creating an editorial calendar, or identifying high-priority content opportunities by buyer stage.

Process

Step 1: Gather Inputs

Ask the user for:

Business Context:

  1. What does the company do?
  2. Who is the ideal customer? (role, industry, pain points, language they use)
  3. What's the primary goal for content? (traffic, leads, brand awareness, thought leadership)
  4. What problems does your product solve?

Customer Research: 5. What questions do customers ask before buying? 6. What objections come up in sales calls? 7. What topics appear repeatedly in support tickets?

Current State: 8. Do you have existing content? What's working? 9. What resources do you have? (writers, budget, time) 10. What content formats can you produce? (written, video, audio)

Competitive Landscape: 11. Who are your main competitors? 12. What content gaps exist in your market?

If the user has previously run competitor-content-analysis, they can reference those outputs for richer competitive data.

Step 2: Define Content Pillars

Content pillars are the 3-5 core topics your brand will own. Each pillar spawns a cluster of related content.

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

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

Most content works fine under /blog with good internal linking. Only use dedicated hub/spoke URL structures for major topics with layered depth.

Step 3: Build Topic Clusters

For each pillar, generate subtopic clusters. Classify every piece of content as:

Searchable content captures existing demand. Optimized for people actively looking for answers.

  • Target a specific keyword or question
  • Match search intent exactly
  • Use clear titles that match search queries
  • Provide comprehensive coverage

Shareable content creates demand. Spreads ideas and gets people talking.

  • Lead with a novel insight, original data, or counterintuitive take
  • Tell stories that make people feel something
  • Create content people want to share to look smart or help others

Content Types:

TypeCategoryBest for
Use-Case ContentSearchableLong-tail keywords — "[persona] + [use-case]"
Hub and SpokeSearchableComprehensive overview + related subtopics
Template LibrariesSearchableHigh-intent keywords + product adoption
Thought LeadershipShareableNaming concepts, challenging conventional wisdom
Data-Driven ContentShareableProduct data analysis, original research
Expert RoundupsShareable15-30 experts answering one question, built-in distribution
Case StudiesBothChallenge → Solution → Results → Key learnings
Meta ContentShareableBehind-the-scenes transparency

Step 4: Map Keywords by Buyer Stage

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

Awareness Stage — "what is," "how to," "guide to," "introduction to"

Consideration Stage — "best," "top," "vs," "alternatives," "comparison"

Decision Stage — "pricing," "reviews," "demo," "trial," "buy"

Implementation Stage — "templates," "examples," "tutorial," "how to use," "setup"

Step 5: Prioritize Content Ideas

Score each idea on four factors:

FactorWeightWhat to evaluate
Customer Impact40%How frequently did this topic come up in research? How emotionally charged?
Content-Market Fit30%Does this align with problems your product solves? Can you offer unique insights?
Search Potential20%Monthly search volume? How competitive? Long-tail opportunities?
Resource Requirements10%Do you have expertise? What additional research is needed?

Step 6: Source Content Ideas

Mine these sources for ideas:

Keyword data: If provided (from Ahrefs, SEMrush, GSC), analyze for topic clusters, buyer stage, intent, quick wins, and content gaps.

Call transcripts: Extract questions, pain points, objections, language patterns, competitor mentions.

Forum research:

  • Reddit: site:reddit.com [topic] — top posts, questions, frustrations
  • Quora: site:quora.com [topic] — most-followed questions
  • Indie Hackers, Hacker News, Product Hunt, industry Slack/Discord

Competitor content: Use web search site:competitor.com/blog to find:

  • Top-performing posts, topics covered repeatedly
  • Gaps they haven't covered
  • Content structure (pillars, categories, formats)
  • Topics you can cover better, angles they're missing

Step 7: Build the Content Plan

Assemble the final strategy.

Output Format

# Content Strategy

**Date:** [current date]
**Company:** [company name]
**Goal:** [primary content goal]
**Audience:** [ICP description]

---

## Content Pillars

### Pillar 1: [Name]
**Rationale:** [why this pillar]
**Connection to product:** [how it ties to what you sell]

Subtopic clusters:
- [Cluster A] — [3-5 topic ideas]
- [Cluster B] — [3-5 topic ideas]
- [Cluster C] — [3-5 topic ideas]

### Pillar 2: [Name]
[Same structure]

### Pillar 3: [Name]
[Same structure]

---

## Priority Topics

| # | Topic/Title | Type | Buyer Stage | Keyword | Priority Score | Why |
|---|-------------|------|-------------|---------|---------------|-----|
| 1 | [title] | [searchable/shareable/both] | [awareness/consideration/decision/implementation] | [keyword] | [X/10] | [customer research backing] |

---

## Topic Cluster Map

[Visual or structured representation of how content interconnects]

---

## Content Calendar (First Month)

| Week | Topic | Type | Format | Buyer Stage | Notes |
|------|-------|------|--------|-------------|-------|
| 1 | | | | | |
| 2 | | | | | |
| 3 | | | | | |
| 4 | | | | | |

---

## Content Gaps vs. Competitors

| Gap | Competitor | Opportunity | Priority |
|-----|-----------|-------------|----------|
| [topic/format they have that you don't] | [who] | [what to do] | [high/med/low] |

---

## Recommended Next Steps

1. [Most important action]
2. [Second action]
3. [Third action]

Rules

  • Every piece of content must be searchable, shareable, or both. Prioritize search — search traffic is the foundation.
  • Specificity beats breadth. "Project management for designers" is better than "project management tips."
  • Content pillars should be broad enough for many subtopics but specific enough to match your product.
  • Don't plan more content than you can produce. A realistic calendar beats an ambitious one that dies in week 3.
  • Prioritize customer impact over search volume. Content that directly addresses known customer pain points converts better than high-volume generic topics.
  • If no customer research exists, recommend gathering it before committing to a full content plan. Even 5 customer interviews dramatically improve content-market fit.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.43%
按下载量换算65

Claude

30.34%
按下载量换算56

Cursor

17.14%
按下载量换算32

Gemini CLI

9.49%
按下载量换算17

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills