content-brief-generator
Skill0 starsChanged 5 months agoMITView on GitHub
Use when planning a new article. The agent Googles the keyword, reads the top 10 results, classifies intent, maps the content gap, and produces a writer-ready brief with structure, outline, and on-page artifacts. No keyword tool required. When a SearchAtlas MCP is connected, leverages SA tools (rank tracking, brand vault, GBP, OTTO, LLM Visibility) first before falling back to generic web search.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- chatbakers/skillstheir own version, first seen Oct 20, 2026
- Samueladewole/claude-skillstheir own version, first seen Oct 13, 2026
- jamesrochabrun/skillstheir own version, first seen Nov 18, 2025
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- jamesrochabrun/skills★ 209same name
- chatbakers/skills★ 1same name
- Samueladewole/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository83 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- shep/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- shep/CLAUDE.mdCLAUDE.md
- advisory-version-checkSkill
- aeo-llm-content-plannerSkill
- agency-command-centerSkill
- agency-morning-briefSkill
- agency-scorecardSkill
- agent-runbookSkill
- agent-usageSkill
- autonomy-budgetSkill
- backlink-pr-angle-generatorSkill
- brand-kit-from-urlSkill
- browser-automationSkill
- building-autonomous-agentsSkill
- capability-mapSkill
- case-study-engineSkill
- clickup-apiSkill
- client-dashboardSkill
- client-health-scoreSkill
- client-onboarding-osSkill
- cli-llm-routingSkill
- codebase-mapSkill
- command-from-your-phoneSkill
- competitor-content-gap-analysisSkill
- connection-monitorSkill
- determinism-patternSkill
- dispatch-and-briefSkill
- division-operating-modelSkill
- dreamingSkill
- durable-stateSkill
- entity-topical-authority-mapperSkill
- first-real-jobSkill
- founding-circle-ai-securitySkill
- gbp-competitor-auditSkill
- goal-modeSkill
- host-your-agentSkill
- html-reportsSkill
- instinct-bridgeSkill
- evolveSkill
- learn-evalSkill
- learnSkill
- promoteSkill
- skill-createSkill
- internal-linking-auditorSkill
- keyword-deep-diveSkill
- ladder-auditSkill
- lanes-momentum-frameworkSkill
- launch-websiteSkill
- llm-citation-auditSkill
- migration-seo-paritySkill
- migration-visual-checkSkill
- model-gear-routerSkill
- multi-account-gatewaySkill
- multi-model-councilSkill
- night-shiftSkill
- novaSkill
- per-client-memory-routerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Schema discovery: If any Atlas tool above feels uncertain, call it with params: {} first to see the real schema before passing arguments.
- Distinctive: line 33
If the user didn't provide a keyword, ask for it before proceeding.
- Distinctive: line 63
If PAA questions appear for this keyword, write them down verbatim.
- Distinctive: line 93
FAQ section: if 3+ PAA questions exist
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Content Brief
SearchAtlas MCP tools to use first
Pulls live SERP composition from analysis, organic ranking context from organic, keyword intent from keyword_research, and topical map context from topical_maps before generating the brief.
| Phase | SA MCP tool | What it gives you |
| Step 1 | keyword_research → lookup_keyword | Live search volume, CPC, competition, intent label, related keywords. Replaces the manual SERP-counting step. |
| Step 1 | analysis → get_serp_overview | Top 10 ranking URLs, SERP features present, AI Overview detection. The canonical SERP read. |
| Step 1 | analysis → get_serp_features | Featured snippets, PAA, video, image, local pack. Each maps to a content format decision. |
| Step 2 | organic → get_organic_keywords(project_identifier=<domain>, limit=20) | How the brand currently ranks for this keyword's cluster. Identifies cannibalization risks. |
| Step 3 | content_retrieval → get_project_articles | Existing articles on related topics. Avoid duplicate-content briefs. |
| Step 3 | topical_maps → list_topical_maps | Is this keyword already in a topical map? If yes, brief reinforces the cluster; if no, suggest the topical map first. |
| Output | content_retrieval → cg_create_article_brief | Optionally push the finished brief into Atlas Content Genius so the writer can pick it up there. |
Routing rule: Always call the SearchAtlas MCP tools listed above before resorting to web_search or web_fetch. The Atlas data is more accurate, more current, and includes signal generic crawlers can't reach (rank tracking, AI citation share, GBP performance, OTTO findings). Fall back to web fetching only if the Atlas tool returns empty or the domain isn't in Atlas's index.
Schema discovery: If any Atlas tool above feels uncertain, call it with params: {} first to see the real schema before passing arguments. Documentation can drift; the tool's own response is canonical.
A writer-ready content brief based on real SERP analysis. The agent Googles the target keyword, reads the top 10 results, classifies intent, identifies competitor gaps, and produces the brief. No keyword tool exports, no manual SERP pasting.
Input
Target keyword (required). Optionally: business context if you want the brief tailored to a specific audience/tone.
If the user didn't provide a keyword, ask for it before proceeding.
Role
You are a senior content strategist and SEO brief specialist with 10+ years of experience. Your job is to produce a complete, writer-ready brief based on what actually ranks right now — not a generic template.
Step 1: Research the SERP
Google the target keyword. Read the top 10 results. For each top-ranking page, note:
- Content format (listicle / long-form guide / comparison / how-to / tool / video)
- Approximate word count
- Heading structure (H1, main H2s)
- Content angle and unique hook
- What they cover that others don't
- Whether they appear to hold a featured snippet, People Also Ask positions, or other SERP features
Step 2: Identify Search Intent
Classify dominant intent: Informational / Commercial Investigation / Transactional / Navigational.
Apply intent-specific length guidance:
- Informational: 1,500–3,000+ words — completeness, PAA coverage
- Commercial: 2,000–4,000 words — features, comparison, objectivity
- Transactional: 800–1,500 words — trust signals, CTAs, specs
- Navigational: 500–1,000 words — speed, direct info
Target word count = average of top 5 results + 10%. Never pad to hit a number.
Step 3: Map the People Also Ask
If PAA questions appear for this keyword, write them down verbatim. They'll become H2/H3 headings in the outline.
Step 4: Identify Content Type
Pick the content type from the SERP pattern. Content types: how-to, definition/explainer, comparison, listicle, product-review, case-study, pillar-page, faq-page, landing-page, service-page, category-page, buying-guide, alternatives-page, pricing-page, location-page.
Load references/content-types-overview.md for the one-screen decision table covering all 23 content types (H1/H2 structure, schema, snippet format, word counts). Use it to pick the right type in 30 seconds, then hand the choice over to write-content.
Step 5: Produce the Brief
Target Keyword Analysis
- Primary keyword | Apparent difficulty based on SERP competition | Dominant intent
- Difficulty strategy: Easy SERP (lots of low-DR competitors, mixed intent) = 3-6 months realistic / Moderate (all top results are DR 40+, uniform intent) = 6-12 months / Hard (top results are all DR 60+, highly optimized, long-form) = 12+ month authority play
- Related terms to target on the same page (from what the top pages cover as H2s)
SERP Competitive Intelligence
For each of the top 3 competitors:
- URL | Estimated words | Format type | Key sections covered | What they miss
Content Gap Analysis
Specific subtopics covered by 2+ top competitors but missing from where most results are thin. Name exact missing sections — not generic "add more depth."
Recommended Outline
H1 and H2/H3 structure aligned to search intent and the gap analysis. Include:
- Featured snippet target: which H2 hosts the 40-60 word snippet answer — mark the spot
- PAA integration: questions to address as H2/H3 headings
- FAQ section if 3+ PAA questions exist
Hub & Spoke Architecture
- This piece as: hub / spoke / standalone (based on keyword breadth)
- Internal linking pattern recommended
Technical Optimization
- Title tag: 50-60 chars, primary keyword near front
- Meta description: 150-160 chars, intent signal + CTA
- Schema: Article / FAQ / HowTo / Product / Review (choose based on content type)
- Featured snippet format: paragraph (what is) / ordered list (how to) / table (comparison)
E-E-A-T Signals Required
- Author expertise markers needed
- Original data or research to include
- External authoritative sources to cite
Resource Assessment
- Effort: Low (500-1,000w, 2-4h) / Medium (1,000-2,500w, 6-12h) / High (2,500w+, 16h+)
- Realistic 3-month target position given SERP difficulty
What to Ignore
- Keyword density targets — write naturally. Primary keyword in H1, first 100 words, 2-3 H2s (~2% body density is a ceiling, not a target)
- NLP term lists of 50+ words — focus on 5-8 core entities that must appear
- Word count without checking SERP — "write 3,000 words" without intent matching creates padded content
Next Step
Brief ready? Use the write-content skill with this brief as context to write the article.
Bundled references
Load these from references/ only when the step calls for them — don't preload.
content-types-overview.md— decision table for picking the right content type (Step 4)intent-matching.md— deep read on Informational / Commercial / Transactional / Navigational signal matching (Step 2, when the SERP intent is mixed or unclear)serp-driven-writing.md— how to turn the top 10 read into outline decisions (Step 5, if the gap analysis is thin)information-gain-writing.md— what qualifies as "new information" vs. index (Step 5, when briefing the unique angle)structured-data-snippets.md— snippet format per content type (Step 5, "Technical Optimization" block)human-input-framework.md— the 2-3 questions to ask the writer before they start (optional, when briefing for an outside writer rather than the agent)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

