Token导航 LogoToken导航

Agent Skill · 研究检索

content-brief-factory(内容简介工厂)

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

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

总安装 238周安装 10GitHub Stars 607下载 83核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/athina-ai/goose-skills --skill content-brief-factory

这个 Skill 是做什么的

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

超越基础关键词要求,提供竞争分析和差异化角度挖掘。适用于需要高质量排名内容的生产场景。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。整合客户真实反馈和 SERP 特征 targeting 策略。确保内容具备市场验证的独特价值主张。

content-brief-factory 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

content-brief-factory 怎么安装?

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

content-brief-factory 支持哪些 AI 工具?

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

content-brief-factory 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

content-brief-factory 是免费的吗?

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

content-brief-factory 用的人多吗?

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

content-brief-factory 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 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-brief-factory

内容简介工厂 · 本页

238607接触敏感数据未明确有提醒

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

SKILL.md 原文

Content Brief Factory

Most content briefs are garbage. They tell you "mention these keywords 7 times" and call it a strategy. This skill produces briefs that include competitive analysis, unique angles mined from what real customers say, SERP feature targeting, and a differentiated outline — so your writer knows exactly what to create and why it'll rank.

Core principle: A great brief doesn't just say "write about X." It says "here's what's already ranking, here's why it's winning, here's the gap they missed, here's the customer language that proves the gap matters, and here's exactly how to structure a page that beats them."

Batch mode: Process 10-50 keywords in a single run. Each brief takes ~30 seconds in enhanced mode, ~60 seconds in baseline.

When to Use

  • "Create content briefs for these keywords"
  • "I need briefs for our Q2 content calendar"
  • "Write briefs for our pSEO templates"
  • "Generate 20 briefs from this keyword list"
  • "What should we write about [topic]? Give me a full brief."

Tool Enhancement (Optional)

Briefs are significantly better with real SERP data (what's actually ranking, what SERP features appear) rather than inferred analysis.

Agent Prompt to User

"I can create strong content briefs using competitive research and customer language mining. For the best results — especially accurate SERP analysis and keyword metrics — I'd recommend connecting a SERP data API." Recommended: SerpAPI (100 free searches/month, $50/month for 5,000) - Sign up at serpapi.com → get API key - Set SERPAPI_KEY env var Alternatives that also work: - Serper.dev (2,500 free searches, then $50/month for 50K) → set SERPER_API_KEY - DataForSEO SERP (pay-per-use, ~$0.01/search) → set DATAFORSEO_LOGIN + DATAFORSEO_PASSWORD - ValueSERP (free tier available) → set VALUESERP_API_KEY "Want to use one of these, or should I proceed with baseline mode? Baseline uses web search to analyze competing pages — still produces great briefs, just with less precise SERP feature and volume data."

Mode Selection

  • Enhanced mode — Real SERP data per keyword: exact ranking pages, SERP features present (featured snippets, PAA, video carousels), search volume, keyword difficulty. Briefs include specific "win this SERP feature" targeting.
  • Baseline mode — Uses web_search to identify top-ranking pages, seo-domain-analyzer for domain metrics. SERP feature detection is inferred. Still produces excellent briefs — the competitive analysis and customer language components don't need SERP APIs.

Phase 0: Intake

  1. Keywords — List of target keywords (1-50). Can be:

- Pasted list - CSV file - Output from seo-opportunity-finder - Output from programmatic-seo-planner (template keywords)

  1. Your site URL — So we check for existing coverage
  2. ICP — Who's reading this content? (role, pain, goal)
  3. Brand voice — Formal/casual/technical? (or link to brand voice doc)
  4. Content type preference — Blog posts, landing pages, guides, glossary entries?
  5. Brief depth — Standard (outline + angle + competitors) or Deep (all of the above + customer quotes + SERP feature targeting + internal links)?
  6. Tool preference — Enhanced mode with SERP API, or baseline? (see Tool Enhancement above)

Phase 1: Existing Coverage Check

Run site-content-catalog on your site:

python3 skills/site-content-catalog/scripts/catalog_content.py \
  --url "<your_site_url>" \
  --output json

For each target keyword, check:

  • Do you already have a page targeting this keyword? → Update brief (not new page)
  • Do you have related pages that should link to this? → Internal link candidates
  • What content gaps exist? → Confirms keyword is worth targeting

Phase 2: Per-Keyword Analysis (Batch)

For each keyword, run in parallel where possible:

2A: SERP Analysis

Enhanced mode (SerpAPI / Serper / DataForSEO):

# SerpAPI example
GET https://serpapi.com/search?q={keyword}&api_key={key}&num=10

Extract per keyword:

  • Top 10 ranking URLs
  • SERP features present (featured snippet, PAA, video, knowledge panel, images)
  • Featured snippet holder (if any) + snippet content
  • People Also Ask questions (top 5)
  • Related searches
  • Search volume + keyword difficulty (if available from API)

Baseline mode:

Use web_search for each keyword:

  • Note top 5-10 results
  • Identify obvious SERP features from result format
  • Use seo-domain-analyzer for volume/difficulty estimates

2B: Competing Page Analysis

For top 3-5 ranking pages per keyword, fetch via fetch_webpage:

Analyze each:

  • Word count — How long are ranking pages?
  • Structure — H1, H2 outline, content flow
  • Content type — How-to, listicle, comparison, guide, definition
  • Unique data — Do they include original research, surveys, screenshots?
  • Freshness — When was it last updated?
  • Depth score — Thin overview vs. comprehensive resource
  • Missing topics — What did they NOT cover that they should have?

2C: Customer Language Mining

Run review-site-scraper + reddit-post-finder for the topic:

# Reviews — find how ICP talks about this problem
python3 skills/capabilities/review-site-scraper/scripts/scrape_reviews.py \
  --platform g2 \
  --url "<relevant_product_review_url>" \
  --output json

# Reddit — find real questions and pain language
python3 skills/reddit-post-finder/scripts/search_reddit.py \
  --subreddit "<relevant_subs>" \
  --keywords "<keyword>,<topic>" \
  --days 365 --sort top --time year

Extract:

  • Real questions people ask about this topic → sections to include
  • Pain language → angle for the intro hook
  • Misconceptions → myth-busting section opportunity
  • Specific use cases → concrete examples to include
  • Quotes → proof points to weave into content

Phase 3: Brief Generation

For each keyword, produce:

# Content Brief: [Target Keyword]

## Metadata
- **Target keyword:** [primary keyword]
- **Secondary keywords:** [2-5 related keywords to include naturally]
- **Search volume:** [monthly, if available] | **Difficulty:** [score, if available]
- **Content type:** [blog post / guide / comparison / glossary / landing page]
- **Target word count:** [X-Y words] (based on competing pages)
- **Priority:** [P0/P1/P2]

---

## Search Landscape

### What's Currently Ranking
| # | Page | Domain | Type | Words | Strengths | Weaknesses |
|---|------|--------|------|-------|-----------|------------|
| 1 | [title] | [domain] | [type] | [count] | [what they do well] | [what they miss] |
| 2 | ... | | | | | |
| 3 | ... | | | | | |

### SERP Features Present
- Featured snippet: [Yes/No — current holder + content]
- People Also Ask: [list of PAA questions]
- Video carousel: [Yes/No]
- Images: [Yes/No]
- Knowledge panel: [Yes/No]

### SERP Feature Targets
- [ ] **Win featured snippet** — Structure answer in [format] under H2 "[heading]"
- [ ] **Answer PAA questions** — Include sections covering: [list]
- [ ] **Image pack** — Include [type of images/diagrams]

---

## Differentiation Angle

**The gap in existing content:** [What ALL ranking pages miss or do poorly]

**Your unique angle:** [How to approach this differently — based on customer language, product positioning, or data you have that competitors don't]

**Customer voice evidence:**
> "[Quote from review/Reddit showing the gap]" — [Source]
> "[Another quote]" — [Source]

---

## Recommended Outline

### Title Options (pick one)
1. [Title option A — SEO-optimized]
2. [Title option B — curiosity-driven]
3. [Title option C — outcome-focused]

### Meta Description
[155 characters, includes keyword, has clear value prop]

### Content Structure

**H1: [Exact H1]**

**H2: [Section 1 — Hook/Problem Statement]**
- What to cover: [specific guidance]
- Length: [~X words]
- Include: [customer pain quote as hook]

**H2: [Section 2 — Core Content]**
- What to cover: [specific guidance]
- Length: [~X words]
- Include: [comparison table / step-by-step / framework]

**H2: [Section 3 — Differentiated Angle]**
- What to cover: [the thing competitors miss]
- Length: [~X words]
- This is your competitive edge

**H2: [Section 4 — Practical Application]**
- What to cover: [concrete examples, use cases]
- Include: [screenshots, templates, or data]

**H2: [Section 5 — FAQ / PAA Answers]**
- [PAA question 1] — [brief answer guidance]
- [PAA question 2] — [brief answer guidance]
- [PAA question 3] — [brief answer guidance]

**H2: [Section 6 — CTA / Next Steps]**
- What to cover: [natural transition to your product]

---

## Internal Linking Plan
- **Link FROM this page TO:** [existing pages that are relevant]
- **Link TO this page FROM:** [existing pages that should reference this]
- **Anchor text suggestions:** [specific anchor text for each link]

---

## Content Requirements
- [ ] Include at least [N] original examples/screenshots
- [ ] Use customer language: "[specific phrases to work in]"
- [ ] Include structured data: [FAQ schema / HowTo schema / etc.]
- [ ] Add last-updated date (for freshness signals)
- [ ] Target readability: [grade level / reading time]

---

## Competitive Advantage Checklist
- [ ] Covers everything top 3 pages cover
- [ ] Adds [unique angle] they all miss
- [ ] Uses real customer language (not generic marketing speak)
- [ ] Targets [SERP feature] with optimized format
- [ ] Has stronger internal linking than competitors
- [ ] Includes original [data/images/templates] competitors lack

Phase 4: Batch Output

For batch runs (10+ briefs):

# Content Brief Batch — [Product/Client] — [DATE]

## Summary
- Briefs generated: [N]
- Total target search volume: [X]/month
- Content types: [N] blog posts, [N] guides, [N] comparisons, etc.

## Priority Order
| # | Keyword | Volume | Difficulty | Content Type | Unique Angle | Status |
|---|---------|--------|-----------|-------------|-------------|--------|
| 1 | [kw] | [vol] | [diff] | [type] | [angle summary] | Ready |
| 2 | [kw] | [vol] | [diff] | [type] | [angle summary] | Ready |
...

## Individual Briefs
[Brief 1]
---
[Brief 2]
---
...

Save to the current working directory or wherever the user prefers. For batch mode, also export a summary CSV.

Cost

ComponentCost
Site catalog (once)~$0.05-0.10
Review scraper (per topic cluster)~$0.10-0.30
Reddit scraper (per topic cluster)~$0.05-0.10
Page fetches (3-5 per keyword)~$0.01-0.03 per keyword
SerpAPI (enhanced, per keyword)~$0.01-0.05 per keyword
Serper.dev (enhanced, per keyword)~$0.001 per keyword
AnalysisFree (LLM reasoning)
Total per brief (baseline)~$0.05-0.15
Total per brief (enhanced)~$0.08-0.25
Batch of 20 briefs (baseline)~$1.00-3.00
Batch of 20 briefs (enhanced)~$1.60-5.00

Tools Required

  • Apify API token — APIFY_API_TOKEN env var
  • Upstream skills: site-content-catalog, seo-domain-analyzer, review-site-scraper, reddit-post-finder, fetch_webpage
  • Optional (enhanced): SerpAPI (SERPAPI_KEY), Serper.dev (SERPER_API_KEY), DataForSEO (DATAFORSEO_LOGIN + DATAFORSEO_PASSWORD), or ValueSERP (VALUESERP_API_KEY)

Scheduling

For ongoing content operations, run weekly:

  • Input: keywords from seo-opportunity-finder or content calendar
  • Output: fresh briefs for the writing team
  • Schedule: Monday mornings before editorial planning

Trigger Phrases

  • "Create content briefs for these keywords"
  • "Brief me on [keyword]"
  • "Generate 20 content briefs"
  • "What should we write about [topic]?"
  • "Build briefs for our content calendar"
  • "Batch brief these keywords"

平台分布

Codex

33.76%
按下载量换算28

Claude

32.6%
按下载量换算27

Cursor

21.23%
按下载量换算18

Gemini CLI

9.64%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

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

继续浏览同类 Skills