Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal…

MITAuto-check passedWriting & Content

Install Blog Brief

skills CLI
$ npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-brief -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Infrasity-Labs/dev-gtm-claude-skills blog-brief --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/blog-brief .claude/skills/blog-brief && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
blog-brief
GitHub stars
136
Token cost
~2.8k tokens
SKILL.md length
556 words
Files
1
Skills in repo
26
Repo updated
First seen
Licence
MIT

At a glance

Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal…

  • Works in 7 steps: Topic Intake → Keyword Research → 5: Template Recommendation → …
  • User says content brief
  • SKILL.md covers Auto-loaded inputs (v1.8.0), Cross-reference and Workflow
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Blog Brief is an agent skill from Infrasity-Labs/dev-gtm-claude-skills. 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…

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering AI search optimization, Content strategy and Blog and article writing. The repository describes itself as: Open-source Claude skills for GEO, AI discoverability, and developer GTM workflows. Built for developer-focused companies that want their documentation to be found, parsed, and… The licence is MIT.

When your agent uses it

  • User says content brief
  • Content outline

Example prompts

  • “content brief”
  • “blog brief”
  • “write brief”
  • “/blog-brief”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Topic Intake
  2. Keyword Research
  3. 5: Template Recommendation
  4. Competitive Analysis
  5. Statistics Research
  6. Generate the Brief
  7. Save the Brief

What it can do on your machine

Read from SKILL.md and the folder at commit 02cfefb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Blog Brief loads about 2.8k tokens when it runs. Until then it costs about 142 tokens; SKILL.md has 556 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~142
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Infrasity-Labs/dev-gtm-claude-skills at commit 02cfefb, republished under its MIT licence (© Infrasity-Labs). 556 words, ~2,782 tokens.

Download SKILL.mdSave it as .claude/skills/blog-brief/SKILL.md (or your agent's skills folder).
name
blog-brief
description
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".
user-invokable
true
argument-hint
<topic>

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 criteria
  • references/distribution-playbook.md: channel-specific distribution tactics
  • references/internal-linking.md: link architecture patterns
  • skills/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:

TemplateBest For
how-to-guideStep-by-step instructional content
listicleCurated lists, ranked items, resource roundups
case-studyIn-depth analysis of a specific example or result
comparisonSide-by-side evaluation of 2+ options
pillar-pageComprehensive topic hub linking to cluster content
product-reviewDetailed evaluation with pros/cons/verdict
thought-leadershipExpert opinion, industry trends, predictions
roundupExpert quotes, tool collections, best-of lists
tutorialTechnical walkthrough with code/config examples
news-analysisTimely coverage with expert commentary
data-researchOriginal data, survey results, benchmark findings
faq-knowledgeQuestion-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
Show full SKILL.md (168 more words)Show less
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.

© Infrasity-Labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/blog-brief of Infrasity-Labs/dev-gtm-claude-skills.

Open the folder on GitHubat commit 02cfefb

Compare with similar skills

Blog Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Blog Brief compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Blog Brief this skillInfrasity-Labs/dev-gtm-claude-skills136—~2.8kAutomated safety check: PassMIT
Blog BriefAgriciDaniel/claude-blog2.3k—~3.2kAutomated safety check: PassMIT
Blog BriefAgriciDaniel/claude-blog2.3k—~3.3kAutomated safety check: PassMIT
Blog WriteAgriciDaniel/claude-blog2.3k—~5.6kAutomated safety check: PassMIT
Blog OutlineAgriciDaniel/claude-blog2.3k1 repos~1.5kAutomated safety check: PassMIT
Blog WriteAgriciDaniel/claude-blog2.3k1 repos~5.6kAutomated safety check: PassMIT

Similar skills

  • Blog Brief

    AgriciDaniel/claude-blog

    Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal…

    2.3k GitHub stars~3.2k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Blog Brief

    AgriciDaniel/claude-blog

    Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal…

    2.3k GitHub stars~3.3k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Blog Write

    AgriciDaniel/claude-blog

    Write new blog articles from scratch optimized for Google rankings and AI citations.

    2.3k GitHub stars~5.6k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Blog Outline

    AgriciDaniel/claude-blog

    SERP-informed outline generation with H2/H3 heading hierarchy, competitive content gap analysis, section-by-section word count targets, chart and image placement markers, optional FAQ question…

    2.3k GitHub starsUsed in 1 repo~1.5k tokens
    Marketing & SEOAuto-check passed
  • Blog Write

    AgriciDaniel/claude-blog

    Write new blog articles from scratch optimized for Google rankings and AI citations.

    2.3k GitHub starsUsed in 1 repo~5.6k tokens
    Writing & ContentAuto-check passed
  • Blog

    AgriciDaniel/claude-blog

    Full-lifecycle blog engine with 31 sub-skills, 12 templates, 100-point scoring, and 5 agents.

    2.3k GitHub stars~6.2k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed

More from Infrasity-Labs/dev-gtm-claude-skills

All 26 skills in this repo
  • Brief Outline Generator

    Infrasity-Labs/dev-gtm-claude-skills

    Generates a fully structured SEO content outline (not a finished brief) and exports it as a formatted .docx Word document.

    136 GitHub stars~4k tokensUpdated 3 mo ago
    Auto-check passed
  • Content Brief

    Infrasity-Labs/dev-gtm-claude-skills

    Generates a fully structured SEO content brief for a target keyword and optionally pushes it to a Notion database.

    136 GitHub stars~2.8k tokensUpdated 3 mo ago
    Auto-check passed
  • API Docs Quality Report

    Infrasity-Labs/dev-gtm-claude-skills

    Audits any API documentation site by crawling every endpoint page and scoring each one across 5 checks: description quality, OpenAPI spec presence, body param descriptions, response codes, and…

    136 GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Docs Auditor

    Infrasity-Labs/dev-gtm-claude-skills

    Audits any developer documentation site across 33 checks in 7 categories and produces a scored report (out of 100) with Pass / Warn / Fail status per check.

    136 GitHub stars~3k tokensUpdated 3 mo ago
    Auto-check passed
  • Growth Report

    Infrasity-Labs/dev-gtm-claude-skills

    Generates a 3-month SEO performance HTML report for any domain using DataForSEO data.

    136 GitHub stars~4k tokensUpdated 3 mo ago
    Auto-check passed
  • Inbox

    Infrasity-Labs/dev-gtm-claude-skills

    Email triage system that handles both one-time setup and recurring triage in a single skill.

    136 GitHub stars~4.8k tokensUpdated 3 mo ago
    Auto-check passed

Questions about Blog Brief

What does Blog Brief do?

Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal…. Blog Brief is an agent skill from Infrasity-Labs/dev-gtm-claude-skills. 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.

When should I use Blog Brief?

Blog Brief fits situations like: user says content brief; content outline.

How do I install Blog Brief in Claude Code?

Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-brief -a claude-code`. Or copy the skill folder (.claude/skills/blog-brief in Infrasity-Labs/dev-gtm-claude-skills) into .claude/skills/blog-brief in your project. Claude Code loads it when a task matches its description.

How do I install Blog Brief in Codex?

Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-brief -a codex`. Or copy the skill folder (.claude/skills/blog-brief in Infrasity-Labs/dev-gtm-claude-skills) into .agents/skills/blog-brief in your project. Codex loads it when a task matches its description.

Can I use Blog Brief in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blog-brief, .gemini/skills/blog-brief, .github/skills/blog-brief and .opencode/skills/blog-brief in your project.

What does Blog Brief need to run?

SKILL.md names no scripts, command-line tools or credentials: Blog Brief is instructions for the agent only.

Does Blog Brief access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Blog Brief safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Blog Brief use?

Blog Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Blog Brief use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Blog Brief?

Skills that share tags, products or a category with Blog Brief: Blog Brief (AgriciDaniel/claude-blog, 2.3k stars), Blog Brief (AgriciDaniel/claude-blog, 2.3k stars), Blog Write (AgriciDaniel/claude-blog, 2.3k stars) and Blog Outline (AgriciDaniel/claude-blog, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Blog Brief?

Infrasity-Labs (a GitHub user) maintains it in Infrasity-Labs/dev-gtm-claude-skills, which has 136 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on June 28, 2026.

Source: Infrasity-Labs/dev-gtm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.