Agent skill · Content & Marketing

content-brief-factory

Generate detailed, differentiated content briefs at scale. Each brief includes SERP analysis, competing page breakdown, unique angles from real customer language (reviews, Reddit), internal linking plan, and SERP feature targets. Batch mode produces 10-50 briefs in one run. Crushes generic "keyword density" briefs from tools like Surfer or Clearscope.

gooseworks-aigithub.com/gooseworks-aiGitHub ↗
claude-codecodexcursorMIT
Install
npx skills add gooseworks-ai/goose-skills --skill content-brief-factory --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Path: skills/content/composites/content-brief-factory/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,091
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the 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 Pr

What's inside
Steps it walks through
  1. When to Use
  2. Tool Enhancement (Optional)
  3. Agent Prompt to User
  4. Mode Selection
  5. Phase 0: Intake
  6. Phase 1: Existing Coverage Check
  7. Phase 2: Per-Keyword Analysis (Batch)
  8. 2A: SERP Analysis
  9. 2B: Competing Page Analysis
  10. 2C: Customer Language Mining
  11. Phase 3: Brief Generation
  12. Phase 4: Batch Output
  13. Cost
  14. Tools Required
Ships with 1 file
  • skill.meta.json
Commands it runs
python3 skills/site-content-catalog/scripts/catalog_content.py \
Reviews — find how ICP talks about this problem
python3 skills/capabilities/review-site-scraper/scripts/scrape_reviews.py \
Reddit — find real questions and pain language
python3 skills/reddit-post-finder/scripts/search_reddit.py \
More from goose-skills
All skills →
About this skill
What does the content-brief-factory skill do?

Generate detailed, differentiated content briefs at scale. Each brief includes SERP analysis, competing page breakdown, unique angles from real customer language (reviews, Reddit), internal linking plan, and SERP feature targets. Batch mode produces 10-50 briefs in one run. Crushes generic "keyword density" briefs from tools like Surfer or Clearscope.

How do I install it?

Run `npx skills add gooseworks-ai/goose-skills --skill content-brief-factory --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From gooseworks-ai/goose-skills, a repository with 1,091 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going