Token导航 LogoToken导航

Agent Skill · 研究检索

content-strategy(内容策略)

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

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

总安装 210周安装 9GitHub Stars 13,231下载 73核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/alirezarezvani/claude-skills --skill content-strategy

这个 Skill 是做什么的

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

专注内容规划与 SEO 优化,驱动流量增长和品牌权威性建设。适用于博客、白皮书、指南类内容的主题策划和发布节奏设计。提供关键词映射、内容集群构建和转化路径对齐方案。content-strategy 属于研究检索类 Skill,可作为该场景下的辅助能力补充。使用前需确认产品市场定位和目标客户画像,避免脱离业务实际。

输出包含可执行日历、优先级矩阵和效果追踪指标建议。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

content-strategy 怎么安装?

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

content-strategy 支持哪些 AI 工具?

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

content-strategy 需要什么权限?

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

content-strategy 是免费的吗?

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

content-strategy 用的人多吗?

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

content-strategy 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 来源仓库有 13,231 星,维护活跃度相对可查。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

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

适不适合你

更适合

  • 已经在用 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

内容策略 · 本页

21013,231只读未明确有提醒

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

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

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

→ See references/content-strategy-reference.md for details

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?

Proactive Triggers

Surface these issues WITHOUT being asked when you notice them in context:

  • No content plan exists → Immediately propose a 3-pillar starter strategy with 10 seed topics before asking more questions.
  • User has content but low traffic → Flag the searchable vs. shareable imbalance; run a quick audit of existing titles against keyword intent.
  • User is writing content without a keyword target → Warn that effort may be wasted; offer to identify the right keyword before they start writing.
  • Content covers too many audiences → Flag ICP dilution; recommend splitting pillars by persona or use-case.
  • Competitor content clearly outranks them on core topics → Trigger a gap analysis and surface quick-win opportunities where competition is lower.

Output Artifacts

When you ask for...You get...
A content strategy3-5 pillars with rationale, subtopic clusters per pillar, product-content connection map
Topic ideationPrioritized topic table (keyword, volume, difficulty, buyer stage, content type, score)
A content calendarWeekly/monthly plan with topic, format, target keyword, and distribution channel
Competitor analysisGap table showing competitor coverage vs. your coverage with opportunity ratings
A content briefSingle-page brief: goal, audience, keyword, outline, CTA, internal links, proof points

Communication

All output follows the structured communication standard:

  • Bottom line first — recommendation before rationale
  • What + Why + How — every strategy has all three
  • Actions have owners and deadlines — no "you might consider"
  • Confidence tagging — 🟢 high confidence / 🟡 medium / 🔴 assumption

Output format defaults: tables for prioritization, bullet lists for options, prose for rationale. Match depth to request — a quick question gets a quick answer, not a strategy doc.


Related Skills

  • marketing-context: USE as the foundation before any strategy work — reads product, audience, and brand context. NOT a substitute for this skill.
  • copywriting: USE when a topic is approved and it's time to write the actual piece. NOT for deciding what to write about.
  • copy-editing: USE to polish content drafts after writing. NOT for planning or strategy decisions.
  • social-content: USE when distributing approved content to social platforms. NOT for organic search strategy.
  • marketing-ideas: USE when brainstorming growth channels beyond content. NOT for deep keyword or topic planning.
  • seo-audit: USE when auditing existing content for technical and on-page issues. NOT for creating new strategy from scratch.
  • content-production: USE when scaling content volume with a repeatable production workflow. NOT for initial strategy definition.
  • content-humanizer: USE when AI-generated content needs to sound more authentic. NOT for topic selection.

平台分布

Codex

37.38%
按下载量换算27

Claude

26%
按下载量换算19

Cursor

19.08%
按下载量换算14

Gemini CLI

8.6%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills