seo-content-brief
Use when generating detailed SEO content briefs. Covers target keywords, search intent, outline (H2/H3), word count, internal links, schema requirements, GEO readiness checklist.
What this skill does
# 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. ```bash 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 ```markdown # 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 readiness - `seo-content` — copywriting 2026 (answer capsules, named entities) - `seo-entity` — entity salience and knowledge graph - `skills/seo/04-geo-2026/content-structure.md` - `skills/seo/06-content-strategy/keyword-research.md`
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".