
Blog Brief
- 1.7k installs
- 1.6k repo stars
- Updated July 23, 2026
- agricidaniel/claude-blog
blog-brief is an agent skill that generates SEO and GEO-optimized blog content briefs with keyword targets, competitive analysis, statistics, outlines, and distribution plans for developers planning high-ranking technica
About
blog-brief is an MIT-licensed agricidaniel/claude-blog skill that produces comprehensive content briefs before writing. It runs six workflow steps: topic intake, keyword research, template selection among 12 content types (how-to, listicle, pillar page, tutorial, data-research, and more), competitive analysis of top-ranking pages, statistics research targeting 8–12 cited stats, and structured brief output with TL;DR drafts, citation capsules, internal link architecture, and multi-channel distribution plans for Reddit, LinkedIn, email, and X. Version 1.8.0 auto-loads DISCOURSE.md themes when present and references a 5-dimension research-quality rubric. Briefs save to briefs/[slug]-brief.md for handoff to /blog write. Use it when planning technical posts optimized for Google rankings and AI citation platforms.
- Audience and intent definition
- Keyword and angle selection
- Deliverable and constraint capture
- Aligns writers and agents
- Reduces draft rework
Blog Brief by the numbers
- 1,703 all-time installs (skills.sh)
- +42 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #317 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/agricidaniel/claude-blog --skill blog-briefAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.7k |
|---|---|
| repo stars | ★ 1.6k |
| Last updated | July 23, 2026 |
| Repository | agricidaniel/claude-blog ↗ |
How do you create an SEO content brief?
Define audience, goal, angle, keywords, and constraints for a blog post before drafting so writers and agents start from an approved brief.
Who is it for?
Developer advocates and technical marketers who want research-backed blog briefs tuned for SEO, AEO, and multi-channel distribution before drafting.
Skip if: Writers who already have a finished draft and only need light copy editing without keyword or competitive research.
When should I use this skill?
User says content brief, blog brief, blog outline, plan blog post, or content outline for a technical article.
What you get
briefs/[slug]-brief.md with keyword map, H2 outline, statistic table, citation capsules, visual plan, and channel distribution checklist.
- content brief markdown file
- keyword and outline plan
- distribution playbook
By the numbers
- Offers 12 selectable content templates for brief recommendations
- Targets 8–12 sourced statistics per planned article
- Six-step workflow from topic intake through brief export
Files
Blog Brief Generator: Content Planning
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)
Auto-loaded inputs (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.
Cross-reference
For evidence-led keyword discovery, audience-avatar prompts, and content prioritization (directly upstream of brief generation), see /blog flow find.
Workflow
Step 1: Topic Intake
Gather from the user: 1. Topic or keyword (required) 2. Target audience (who reads this?) 3. Search intent: Informational, commercial, transactional, navigational 4. Business context: What does the company do? What's the CTA?
If only a topic is given, infer the rest from context.
Step 2: Keyword Research
Using WebSearch: 1. Search for the target keyword; analyze what currently ranks 2. Identify primary keyword (exact match target) 3. Identify 3-5 secondary keywords (related terms, long-tail) 4. Identify 3-5 question queries (People Also Ask style) 5. Note the search intent: what do searchers actually want?
Step 2.5: Template Recommendation
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: 1. Match search intent to template strength 2. Check what format top-ranking competitors use 3. Consider the user's available assets (data, expertise, tools) 4. Load the matching template file from templates/[type].md 5. Include the template name in the brief output
Step 3: Competitive Analysis
Analyze the top 3-5 ranking pages for the target keyword: 1. Content length: What's the average word count? 2. Heading structure: How many H2s? What topics do they cover? 3. Visual elements: Do competitors use charts, images, videos? 4. Content gaps: What do all competitors miss? 5. Freshness: How recently were they updated? 6. Schema: Do they use FAQ or other rich results? (Note: HowTo deprecated Sept 2023) 7. Template pattern: What content format do top results use?
Step 4: Statistics Research
Find 8-12 statistics the article should include: 1. Search: [topic] study 2025 2026 data statistics research 2. Prioritize tier 1-3 sources 3. For each stat, record: value, source, URL, date, methodology 4. Identify 2-4 stats suitable for chart visualization 5. Identify 1-2 stats suitable for TL;DR and social sharing
Step 5: Generate the Brief
Output 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]Step 6: Save the Brief
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.
Related skills
How it compares
Use blog-brief for research-heavy SEO planning; switch to direct writing skills once the brief and keyword map are approved.
FAQ
How many content templates does blog-brief offer?
blog-brief recommends one of 12 templates—including how-to-guide, listicle, comparison, pillar-page, tutorial, and data-research—based on search intent and competitor formats. Each maps to a templates/[type].md file referenced in the brief output.
Where does blog-brief save the finished brief?
blog-brief saves output to briefs/[slug]-brief.md in the project unless the user specifies another path. The brief includes keyword targets, H2 outline, statistic table, visual plan, and distribution checklist ready for /blog write.