blog-outline

blog-outline is a skill for Claude Code from Infrasity-Labs/dev-gtm-claude-skills. It costs 146 tokens per session (1,228 once invoked), scanned A, original, MIT.

A planning tool that turns a blog topic and target search phrase into a structured outline. SERP means the search-results page shown by a search engine.

In plain words
What is it for?
Use it to plan H2 and H3 headings, section lengths, visual placements, FAQs, and internal-link locations.
Why use it?
It helps reveal what competing pages cover and where your article can add missing information before writing begins.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the marketing-skills plugin — 116 skills, 8 commands, 23 agents, 1 hook shipped together , and of writing-skills

Good fit Use it to plan H2 and H3 headings, section lengths, visual placements, FAQs, and internal-link locations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/infrasity-labs/dev-gtm-claude-skills/blog-outline
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-outline
Clone the repo
git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills

Made for: Claude Code.

Or install marketing-skills, the plugin that ships this one along with the rest of its 116 skills, 8 commands, 23 agents, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for blog-outline

README.md
[![agentmods](https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/blog-outline/github.svg)](https://agentmods.dev/skills/infrasity-labs/dev-gtm-claude-skills/blog-outline)
Your own site
<a href="https://agentmods.dev/skills/infrasity-labs/dev-gtm-claude-skills/blog-outline"><img src="https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/blog-outline/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for blog-outline

Your own site · 80×15
<a href="https://agentmods.dev/skills/infrasity-labs/dev-gtm-claude-skills/blog-outline"><img src="https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/blog-outline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 146 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,228 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00146 $0.01228
Opus 5 $0.00073 $0.00614
Sonnet 5 $0.00029 $0.00246
Haiku 4.5 $0.00015 $0.00123

Measured 9d ago against content hash 2f019fa84457, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

blog-outline scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/blog-outline/SKILL.md · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Blog Outline Generator: SERP-Informed Structure Planning

Generates skeletal blog post outlines informed by SERP analysis. A lighter alternative to a full content brief - produces heading hierarchy, section targets, and content gap notes without deep statistics research or full competitive analysis.

Cross-reference

For evidence-led topical-relevance and content-planning prompts upstream of outlining, see /blog flow find. The blog-post-outline-prompt under /blog flow optimize is a complementary structural reference.

Workflow

Step 1: Topic & Intent

Gather from the user:

  1. Topic or target keyword (required)
  2. Target keyword - the exact phrase to rank for (if different from topic)
  3. Search intent - Informational, commercial, or transactional

If only a topic is given, infer the keyword and intent from context.

Step 2: SERP Analysis

Use WebSearch to analyze the top 5 results for the target keyword:

  1. Search for the target keyword

  2. For each of the top 5 results, note:

    • Heading structure - H2/H3 topics covered
    • Content length - Approximate word count
    • Visual elements - Charts, images, videos, infographics
    • FAQs - Any FAQ sections or People Also Ask coverage
    • Unique angles - What makes each result distinct
    • Gaps - What's missing or weak
  3. Use WebFetch on the top 2-3 results to extract detailed heading structures if the search snippets are insufficient.

  4. Compile a summary of common patterns and missed opportunities.

Step 3: Generate Outline

Create a structured outline with the following format:

# Outline: [Topic]

## Title Suggestions
1. [Primary title - 40-60 chars, front-loaded keyword, power word]
2. [Alternative title - different angle]
3. [Alternative title - question format]

## Target Parameters
- **Primary keyword**: [keyword]
- **Search intent**: [Informational/Commercial/Transactional]
- **Target word count**: [X,XXX] words
- **H2 sections**: [6-8]
- **Target reading level**: Flesch 60-70

---

## Outline

### H2: [Section Title - Question Format] (~300-400 words)
- **Answer-first opener**: [What stat or fact should open this section?]
- **Key points to cover**:
  - [Point 1]
  - [Point 2]
  - [Point 3]
- **H3: [Subsection]** (if appropriate)
  - [What this subsection covers]
- **Key statistic to find**: [What data point would strengthen this section?]
- **Chart suggestion**: [Bar/Line/Donut/None] - [What data to visualize]
- **Image placement**: [Yes/No] - [Description of recommended image]

### H2: [Section Title] (~300-400 words)
[... repeat for 6-8 sections ...]

### FAQ Section (3-5 items)
1. [Question from People Also Ask] - [Brief answer direction]
2. [Question from People Also Ask] - [Brief answer direction]
3. [Question from People Also Ask] - [Brief answer direction]
4. [Question from SERP analysis] - [Brief answer direction]

### Conclusion (~100-150 words)
- Key takeaways to summarize
- Call to action direction

---

## Internal Linking Zones
- **Link TO from this post**: [Existing content that should be referenced]
- **Link FROM to this post**: [Existing content that should link here]

## Content Gaps to Exploit
1. [What competitors miss that this post should cover]
2. [Unique angle or original perspective to include]
3. [Format advantage - visuals, depth, or structure competitors lack]

Read the full file on GitHub · 140 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 140 lines · 146 tokens per session scan A 2f019fa84457

Subscribe to this mod's changes

blog-outline is a skill published in the GitHub repository Infrasity-Labs/dev-gtm-claude-skills (124 stars, last pushed 2mo ago), licensed MIT. It adds 146 tokens to every session and 1,228 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

geo-audit

Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit across AI citability, platform analysis, technical infrastructure, content quality, and schema markup. Produces a composite GEO Score (0-100) with prioritized action plan.

techhorizonlabs/thl-open · 60 tokens

geo

GEO-first SEO analysis tool. Optimizes websites for AI-powered search engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews) while maintaining traditional SEO foundations. Performs full GEO audits, citability scoring, AI crawler analysis, llms.txt generation, brand mention scanning, platform-specific…

techhorizonlabs/thl-open · 139 tokens

geo-brand-mentions

Brand mention and authority scanner for AI visibility. Analyzes brand presence across platforms that AI models rely on for entity recognition and citation decisions. Produces a Brand Authority Score (0-100) with platform-specific recommendations.

techhorizonlabs/thl-open · 49 tokens

geo-llmstxt

Analyzes and generates llms.txt files -- the emerging standard for helping AI systems understand website structure and content. Can validate existing llms.txt files or generate new ones from scratch by crawling the site.

techhorizonlabs/thl-open · 46 tokens

agent-readiness-scan

Use when a client audit, GEO/AI-visibility snapshot, or remediation re-scan needs the Cloudflare agent-readiness score from isitagentready.com — e.g. Theo client audits, "is the site agent-ready", markdown negotiation / MCP / llms.txt / Content-Signal checks, or tracking score deltas after Tier 0/1 fixes.

techhorizonlabs/thl-open · 79 tokens

found-by-ai

Measure whether AI engines actually recommend a business when buyers ask. Runs the free live scan at areyoufoundbyai.com (no auth, 60s), reads the verdict and the rivals AI names instead, hands back the fix plan, and wires monitored sites into a fix-and-re-measure loop over MCP.

techhorizonlabs/thl-open · 67 tokens