Seo content brief
Redefining development through cognitive automation and collaborative agent systems.
npx -y skills add fusengine/agents --skill seo-content-briefAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when generating a detailed SEO content brief for a single page or topic before writing.
SKILL.md
4.5 KB, as published. Nobody here has run it
Content Brief Generator
Content Intelligence First
Before generating a brief, run scripts/analyze-keywords.ts (local-first, no API key) on the target or a top competitor URL. Use the result to shape target keywords, semantic variants, heading coverage, local modifiers, and stuffing warnings.
bun run scripts/analyze-keywords.ts <url-or-path> --keyword "<primary keyword>" --synonyms "<syn1,syn2>" --locations "<city1,city2>" --format markdown
Metadata and Heading Rules
- Meta title must be 60 characters or less.
- Meta description must be 150 characters or less.
- Do not include the company or brand name in the meta title unless the client explicitly asks. If useful, provide a branded variant as an option or exception.
- Meta title and H1 should be semantically similar, but not necessarily identical.
- Meta title and H1 need the primary keyword or a strong variant.
- H2/H3 headings should distribute synonyms, long-tail phrases, questions, and sub-intents.
- Avoid repeating the exact keyword across every heading.
Long-Tail by Buyer State (2026)
Layer keywords by buyer state, not by surface similarity:
| Layer | State | Intent signal | Example phrasing |
|---|---|---|---|
| L1 | Awareness | "what is", "why", symptoms, problems | broad informational, conversational |
| L2 | Comparison | "vs", "alternatives", "best for" | options weighing |
| L3 | Evaluation | "pricing", "reviews", "is X worth it" | scrutiny, objections |
| L4 | Decision | "buy", "near me", "demo", "signup" | transactional/local |
One brief targets one buyer state per URL. Cluster by buyer state + intent, never by lexical surface similarity.
Citation eligibility
AI Overviews capture ~30-60% of the informational CTR. Optimize for verbatim LLM extraction, not raw traffic alone: every section must yield a self-contained, quotable answer. A brief that ranks but is not extractable loses the AI Overview slot.
Brief Structure
# Content Brief: <topic>
## Target Keywords
- Primary: <kw> (vol, KD, intent)
- Secondary: <kw1>, <kw2>, <kw3>
- Long-tail: <lt1>, <lt2>, <lt3>
## Search Intent
- Type: informational | navigational | commercial | transactional
- User question: "<exact question>"
- Expected format: guide | listicle | comparison | tutorial
## Outline
- Meta title: <primary keyword or strong variant, <=60 chars, no brand unless requested>
- Meta description: <benefit + intent match, <=150 chars>
- H1: <semantic match to title, primary keyword or strong variant>
- H2: <synonym, long-tail phrase, question, or sub-intent>
- H3: <supporting sub-intent>
- H2: <section 2>
- H2: FAQ
- H2: Conclusion
## Answer Capsules (per H2)
<40-60 word self-contained answer opening EACH H2, not only the first 100 words — citation-eligible for AI Overviews>
## Word Count Target
<based on top 10 SERP average>
## Internal Links (5-10)
- → <pillar page>
- → <related cluster pages>
## Schema
- Article + BreadcrumbList (always)
- FAQPage (if FAQ section)
- VideoObject (if video embed)
## GEO Requirements
- Answer capsule (40-60 words) opening every H2
- One hyperlinked statistic to its primary source every 150-200 words
- Name key entities explicitly (no pronouns for the primary entity)
- Cite 3-5 authoritative sources
- Use tables/lists for comparison data
References
seo-geo— AI Overviews / LLM readinessseo-content— copywriting 2026 (answer capsules, named entities)seo-entity— entity salience and knowledge graphskills/seo/04-geo-2026/content-structure.mdskills/seo/06-content-strategy/keyword-research.md
Gives 0 of the 12 instructions most plan spec skills give
Counted across 1,100 of the 1,860 authors here whose files we hold, read 2026-08-06
- ask one question at a timein 46 of 1100, across 38 files
- Break plans into vertical slicesin 28 of 1100, across 10 files
- Publish issues in dependency orderin 27 of 1100, across 9 files
- Iterate until user approves the breakdownin 24 of 1100, across 6 files
- Explore the repository to understand the codebase statein 24 of 1100, across 7 files
- Use domain glossary vocabularyin 23 of 1100, across 5 files
- Apply correct triage labels to published issuesin 23 of 1100, across 5 files
- Write failing tests before implementation codein 23 of 1100, across 18 files
- Prefer AFK slices over HITLin 22 of 1100, across 7 files
- ask clarifying questions until requirements are concretein 21 of 1100, across 13 files
- Respect existing architecture decision recordsin 20 of 1100, across 5 files
- write a specification before writing any codein 20 of 1100, across 12 files
Said here and by no other author read
- Run keyword analysis before generating the brief
- Target one buyer state per URL
- Keep the meta title under 60 characters
- Keep the meta description under 150 characters
- Exclude brand name from meta title unless requested
- Include the primary keyword in the meta title and H1
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.