skills/blog-brief/SKILL.md
Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal linking architecture, template recommendations (12 types), TL;DR drafts, citation capsule planning, information gain prompts, and multi-channel distribution plans. Briefs are optimized for Google rankings and AI citations (GEO/AEO). Use when user says "content brief", "blog brief", "write brief", "outline blog", "plan blog post", "blog outline", "content outline".
npx skillsauth add agricidaniel/claude-blog blog-briefInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generates comprehensive content briefs that guide blog writing for maximum impact on both Google rankings and AI citation platforms.
Reference documents:
references/content-templates.md: template selection criteriareferences/distribution-playbook.md: channel-specific distribution tacticsreferences/internal-linking.md: link architecture patternsskills/blog/references/research-quality.md - 5-dim quality rubric, pre-flight trap classes, freshness floors (v1.8.0; cross-skill ref lives in the orchestrator's references dir)skills/blog/references/synthesis-contract.md - 6 LAWs for synthesis output (v1.8.0)When DISCOURSE.md is present at the project root (produced by /blog discourse), load it before starting brief generation. Use the discourse brief's "What's NEW" themes, "Consensus" themes, and "Contrarian takes" sections to enrich the competitive landscape and information-gain sections of this brief. Cite from DISCOURSE.md using the same inline [name](url) pattern. If DISCOURSE.md is absent, behavior is unchanged.
For evidence-led keyword discovery, audience-avatar prompts, and content prioritization (directly upstream of brief generation), see /blog flow find.
Gather from the user:
If only a topic is given, infer the rest from context.
Using WebSearch:
Analyze the topic, search intent, and competitive landscape to recommend one
of 12 content templates. Load references/content-templates.md for selection
criteria.
Available templates:
| Template | Best For |
|----------|----------|
| how-to-guide | Step-by-step instructional content |
| listicle | Curated lists, ranked items, resource roundups |
| case-study | In-depth analysis of a specific example or result |
| comparison | Side-by-side evaluation of 2+ options |
| pillar-page | Comprehensive topic hub linking to cluster content |
| product-review | Detailed evaluation with pros/cons/verdict |
| thought-leadership | Expert opinion, industry trends, predictions |
| roundup | Expert quotes, tool collections, best-of lists |
| tutorial | Technical walkthrough with code/config examples |
| news-analysis | Timely coverage with expert commentary |
| data-research | Original data, survey results, benchmark findings |
| faq-knowledge | Question-driven reference content |
Selection process:
templates/[type].mdAnalyze the top 3-5 ranking pages for the target keyword:
Find 8-12 statistics the article should include:
[topic] study 2025 2026 data statistics researchOutput format:
# Content Brief: [Title Suggestion]
## Template
**Recommended**: [template-name]: [1-sentence rationale]
**Template file**: `templates/[type].md`
## Target Keywords
- **Primary**: [keyword]: [estimated monthly search volume if available]
- **Secondary**: [keyword 1], [keyword 2], [keyword 3]
- **Questions**: [question 1], [question 2], [question 3]
## Search Intent
[Informational/Commercial/Transactional]: [1-2 sentence explanation of
what the searcher wants]
## Content Parameters
- **Word count**: [2,000-2,500] words
- **Reading level**: Flesch 60-70 (expert-accessible)
- **Format**: [Markdown/MDX/HTML]
- **H2 sections**: [6-8]
- **Images**: 3-5 from Pixabay/Unsplash
- **Charts**: 2-4 via built-in blog-chart (diverse types)
- **FAQ items**: 3-5
## Recommended Title
[Question-format title including primary keyword, under 60 chars]
Alternative titles:
1. [Option 2]
2. [Option 3]
## Meta Description
[150-160 chars, fact-dense, includes 1 statistic, ends with value proposition]
## TL;DR Draft
> **TL;DR:** [40-60 word summary with key finding + 1 statistic + source.
> Should be self-contained; a reader who only reads this box gets the
> core value of the article.]
## Information Gain Opportunities
- **[ORIGINAL DATA]**: [Suggestion for proprietary data, survey, experiment,
or benchmark the author can produce to differentiate this post]
- **[PERSONAL EXPERIENCE]**: [Suggestion for first-hand observation, test
result, or case study to include: "When we tested X, we found Y"]
- **[UNIQUE INSIGHT]**: [Suggestion for contrarian take, novel analysis,
or non-obvious connection that competitors have not covered]
## Content Outline
### Introduction (100-150 words)
- Hook: [Surprising statistic to open with]
- Problem: [What challenge does the reader face?]
- Promise: [What will they learn?]
- TL;DR box placement (after hook, before first H2)
### H2: [Question Format] (300-400 words)
- **Answer-first**: Open with [specific stat + source]
- Cover: [subtopic 1], [subtopic 2]
- **Image**: [Description of recommended image]
- **Key stat**: [Specific statistic to include]
### H2: [Question Format] (300-400 words)
- **Answer-first**: Open with [specific stat + source]
- Cover: [subtopic 1], [subtopic 2]
- **Chart**: [Type] showing [data description]
- **Key stat**: [Specific statistic to include]
[... repeat for 6-8 sections ...]
### FAQ Section (3-5 items)
1. [Question]: Answer with [stat + source]
2. [Question]: Answer with [stat + source]
3. [Question]: Answer with [stat + source]
### Conclusion (100-150 words)
- Key takeaways (bulleted)
- Call to action: [What should the reader do next?]
## Statistics to Include
| # | Statistic | Source | Year | Section |
|---|-----------|--------|------|---------|
| 1 | [stat] | [source + URL] | 2025 | H2: Section 1 |
| 2 | [stat] | [source + URL] | 2026 | H2: Section 2 |
| ... | ... | ... | ... | ... |
## Citation Capsule Plan
For each H2, plan a 40-60 word self-contained passage optimized for AI
extraction. Each capsule should include a stat, its source, and a clear
claim that can stand alone when quoted.
| Section | Capsule Focus | Key Stat | Source |
|---------|--------------|----------|--------|
| H2: [Section 1] | [Core claim this section makes] | [stat] | [source] |
| H2: [Section 2] | [Core claim this section makes] | [stat] | [source] |
| H2: [Section 3] | [Core claim this section makes] | [stat] | [source] |
| ... | ... | ... | ... |
## Cover Image
| Option | Details |
|--------|---------|
| Photo cover | [Pixabay/Unsplash/Pexels search terms for wide hero image] |
| Generated SVG | [Text-on-gradient concept with key stat, if data-heavy topic] |
| Dimensions | 1200x630 (OG-compatible) |
## Visual Element Plan
| # | Type | Data | Section |
|---|------|------|---------|
| 1 | [Bar chart] | [Data description] | H2: Section 2 |
| 2 | [Donut chart] | [Data description] | H2: Section 4 |
| 3 | [Image: Pixabay] | [Search terms] | H2: Section 1 |
| 4 | [Image: Pixabay] | [Search terms] | H2: Section 3 |
## Competitive Gaps to Exploit
1. [What competitors miss that we should cover]
2. [Unique angle or original data we can provide]
3. [Format advantage: charts/visuals competitors lack]
## Internal Link Architecture
- **Link TO** (from this new post to existing pages):
1. [Page title/URL] - anchor text: "[descriptive anchor]"
2. [Page title/URL] - anchor text: "[descriptive anchor]"
3. [Page title/URL] - anchor text: "[descriptive anchor]"
4. [Page title/URL] - anchor text: "[descriptive anchor]"
5. [Page title/URL] - anchor text: "[descriptive anchor]"
- **Link FROM** (update these existing pages to link to this new post):
1. [Page title/URL] - anchor text: "[descriptive anchor]"
2. [Page title/URL] - anchor text: "[descriptive anchor]"
3. [Page title/URL] - anchor text: "[descriptive anchor]"
4. [Page title/URL] - anchor text: "[descriptive anchor]"
5. [Page title/URL] - anchor text: "[descriptive anchor]"
- **Pillar connection**: [Which pillar page this belongs to, if applicable]
- **Cluster position**: [Hub / Spoke / Standalone]
## E-E-A-T Signals to Include
- **Experience**: [First-hand insight, case study, or test result]
- **Expertise**: [Author credentials relevant to topic]
- **Authority**: [Industry recognition, citations, partnerships]
- **Trust**: [Transparency, sourced data, no self-promotion]
## Distribution Plan
- **Reddit**: [Specific subreddits (r/sub1, r/sub2), posting approach (value-first
comment vs. link post), authentic participation strategy, timing]
- **YouTube**: [Video companion concept, estimated length, key visuals from the
post to reuse, thumbnail idea]
- **LinkedIn**: [Article excerpt angle, target audience segment, best posting
time for the niche, engagement hook]
- **Email**: [Newsletter excerpt (2-3 sentences), subject line suggestion,
CTA linking back to the full post]
- **Twitter/X**: [Thread hook (first tweet), 3-5 key tweet ideas built from
statistics in the post, hashtag suggestions]
Save to the user's project as briefs/[slug]-brief.md or to a location
they specify. Confirm the brief is ready for /blog write.
development
Research what people are actually saying about a topic in the last 30 days across Reddit, X / Twitter, YouTube, Hacker News, dev.to, Medium, and other public discourse platforms. API-free; uses WebSearch with platform-targeted site operators plus recency filters. Produces DISCOURSE.md (a structured brief) and JSON output the writer can consume. Complements blog-researcher (which focuses on authority sources) with a recency-and-engagement lens. Use when user says "blog discourse", "discourse research", "what are people saying about", "research what people are saying", "voice of customer", "social listening", "30-day research", "trend research", "what's the discussion on", "real-time research", "practitioner discourse", "/blog discourse".
documentation
Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, all blog sub-skills auto-load these files before writing or reviewing. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog".
testing
Translate existing blog posts into one or more target languages with SEO-optimized localization. Produces native-quality translations that preserve markdown structure, frontmatter, schema JSON-LD, image and chart embeds, and citation capsules. Localizes keywords, meta tags, numbers, dates, currencies, and quote styles per locale. Flags machine-translation artifacts for review. Run BEFORE blog-localize: this handles language conversion; localize handles cultural adaptation after translation completes. Use when user says "translate blog", "blog translate", "uebersetzen", "traduire", "traducir", "translate post", "blog auf Deutsch", "blog en espanol".
testing
One-command multilingual blog creation. Writes a blog post, translates it into user-specified languages, applies cultural adaptation, and emits hreflang tags, sitemap entries, and a CMS-ready language map. The complete write-to-publish pipeline for international content. Orchestrates blog-write, blog-translate, blog-localize, and (optionally) seo-hreflang. Use when user says "multilingual blog", "blog multilingual", "write in multiple languages", "international blog", "mehrsprachiger Blog", "blog multilingue", "blog multilingue", "create blog in German and French".