Token导航 LogoToken导航

Agent Skill · 研究检索

content-strategy(内容策略)

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

content-strategy 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 52,586。

总安装 552周安装 23GitHub Stars 35下载 184核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

content-strategy 辅助文档与内容整理,支持 Markdown、README 等格式优化。适用于提炼结构、统一术语或重组零散材料,提升可读性与一致性。使用时需保留项目已有事实,避免将未确认信息写成确定结论。涉及对外文案时应控制语气,防止过度营销或夸大能力描述。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/content-strategy

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/superamped/ai-marketing-skills --skill content…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

content-strategy 怎么安装?

在终端执行 npx skills add https://github.com/superamped/ai-marketing-skills --skill content-strategy。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

content-strategy 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

content-strategy 需要什么权限?

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

content-strategy 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

content-strategy 用的人多吗?

公开数据是累计安装 552 次,近一周安装 23 次,下载 184 次,GitHub 35 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

content-strategy 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
content-strategy

内容策略 · 本页

55235只读未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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.

平台分布

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 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills