blog-brief
Skill0 starsChanged 3 months agoMITView on GitHub
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".
5 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- gaznilmuzammil12-prog/seo-skills-by-gaznilword for word, first seen Nov 16, 2026
- alpit-patel/seo-aeo-geo-kitedited, first seen Nov 8, 2026
- AgriciDaniel/claude-blogedited, first seen Oct 25, 2026
- coopersimson96/ai-content-systemedited, first seen Jun 25, 2026
- megastep/codex-skillsedited, first seen Feb 25, 2026
Other versions5 projects use a version of this.
Word for word · 1
- gaznilmuzammil12-prog/seo-skills-by-gaznil★ 0100% same
Edited · 4
- AgriciDaniel/claude-blog★ 2.7k51% same
- coopersimson96/ai-content-system★ 1798% same
- megastep/codex-skills★ 497% same
- alpit-patel/seo-aeo-geo-kit★ 265% same
Wrote their own version · 0
None found.
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 repository85 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/llms-full.txtllms.txt
- docs/llms.txtllms.txt
- llms-full.txtllms.txt
- llms.txtllms.txt
- ab-testingSkill
- accessibilitySkill
- ai-seoSkill
- analyticsSkill
- attributionSkill
- blog-analyzeSkill
- blog-audioSkill
- blog-auditSkill
- blog-brandSkill
- blog-calendarSkill
- blog-cannibalizationSkill
- blog-chartSkill
- blog-clusterSkill
- blog-discourseSkill
- blog-factcheckSkill
- blog-flowSkill
- blog-geoSkill
- blog-googleSkill
- blog-imageSkill
- blog-locale-auditSkill
- blog-localizeSkill
- blog-multilingualSkill
- blog-notebooklmSkill
- blog-outlineSkill
- blog-personaSkill
- blog-repurposeSkill
- blog-rewriteSkill
- blog-schemaSkill
- blog-seo-checkSkill
- blogSkill
- blog-strategySkill
- blog-taxonomySkill
- blog-translateSkill
- blog-writeSkill
- canonical-tagSkill
- competitorsSkill
- content-optimizationSkill
- content-strategySkill
- copywritingSkill
- core-web-vitalsSkill
- croSkill
- directory-submissionsSkill
- eeat-signalsSkill
- entity-seoSkill
- featured-snippetSkill
- google-search-consoleSkill
- heading-structureSkill
- indexingSkill
- indexnowSkill
- internal-linksSkill
- keyword-researchSkill
- local-seoSkill
- meta-descriptionSkill
- mobile-friendlySkill
- open-graphSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. 4 are common, 2 are distinctive, and 0 are very specific to this project.
4
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 47
If only a topic is given, infer the rest from context.
- Common: line 52
Search for the target keyword.
- Common: line 82
Check what format top-ranking competitors use
- Common: line 83
Consider the user's available assets (data, expertise, tools)
- Distinctive: line 92
Visual elements: Do competitors use charts, images, videos?
- Distinctive: line 95
Schema: Do they use FAQ or other rich results?
“Common” is measured: kept by at least 6 in 10 of the 4 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
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:
- Topic or keyword (required)
- Target audience (who reads this?)
- Search intent: Informational, commercial, transactional, navigational
- 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:
- Search for the target keyword; analyze what currently ranks
- Identify primary keyword (exact match target)
- Identify 3-5 secondary keywords (related terms, long-tail)
- Identify 3-5 question queries (People Also Ask style)
- 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:
- Match search intent to template strength
- Check what format top-ranking competitors use
- Consider the user's available assets (data, expertise, tools)
- Load the matching template file from
templates/[type].md - Include the template name in the brief output
Step 3: Competitive Analysis
Analyze the top 3-5 ranking pages for the target keyword:
- Content length: What's the average word count?
- Heading structure: How many H2s? What topics do they cover?
- Visual elements: Do competitors use charts, images, videos?
- Content gaps: What do all competitors miss?
- Freshness: How recently were they updated?
- Schema: Do they use FAQ or other rich results? (Note: HowTo deprecated Sept 2023)
- Template pattern: What content format do top results use?
Step 4: Statistics Research
Find 8-12 statistics the article should include:
- Search:
[topic] study 2025 2026 data statistics research - Prioritize tier 1-3 sources
- For each stat, record: value, source, URL, date, methodology
- Identify 2-4 stats suitable for chart visualization
- 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.
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.

