# seo-content-brief

Turns a target keyword into a full SEO brief: search intent, SERP breakdown, heading outline and a writer checklist. Useful when content goes to an outside author.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 449 installs · ★ 721
- Author: OpenClaudia
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/OpenClaudia/openclaudia-skills/tree/HEAD/skills/seo-content-brief/SKILL.md
- Updated: 2026-10-21
- HTML: https://affpapa.org/en/nevibecode/skills/openclaudia-seo-content-brief

## What it does

The skill takes a keyword and builds a brief a writer can work from. It searches the query with WebSearch, classifies intent as informational, commercial, transactional or navigational, then reads the top 5–10 results for format, rough length and the H2 topics everyone covers.

What comes back is a markdown document: a keyword table with volume and CPC, content specs (type, word count, audience, tone), title and meta description requirements, an H1–H3 tree with per-section notes, an FAQ block aimed at featured snippets, and a visual content table. The writer checklist at the end covers things like keyword density and internal link count.

With `SEMRUSH_API_KEY` set, it pulls keyword, related-term and question data from the SemRush API. Without the key it falls back to SERP analysis and People Also Ask questions, so volume and difficulty columns stay empty. The source instructions cut off mid-sentence about a SERP being dominated, so that case is not covered.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add OpenClaudia/openclaudia-skills --skill seo-content-brief -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/seo-content-brief/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/seo-content-brief/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add OpenClaudia/openclaudia-skills --skill seo-content-brief -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/seo-content-brief/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add OpenClaudia/openclaudia-skills --skill seo-content-brief -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/seo-content-brief/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install OpenClaudia/openclaudia-skills seo-content-brief
```

2. **Manually: put the files in place**
- File: `.github/skills/seo-content-brief/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add OpenClaudia/openclaudia-skills --skill seo-content-brief -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/OpenClaudia/openclaudia-skills --path skills/seo-content-brief
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/seo-content-brief/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add OpenClaudia/openclaudia-skills --skill seo-content-brief -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/OpenClaudia/openclaudia-skills/tree/HEAD/skills/seo-content-brief/SKILL.md

## When to use it
- hand a structured brief to a freelance writer
- classify search intent before picking a format
- map the top results by format and length
- draft an H1–H3 outline with secondary keywords
- build an FAQ block for featured snippets

## Example prompts
- create a content brief for "best standing desk for small apartments"
- I need an SEO brief for a comparison post on project management tools
- write a writer brief for the keyword "how to set up a VPN on a router"

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 6a4dee4254bb5597.

BEGIN THIRD-PARTY FILE 6a4dee4254bb5597
````text
---
name: seo-content-brief
description: Create an SEO content brief for writers. Use when the user says "content brief", "SEO brief", "writing brief", "brief for", "writer brief", "outline for SEO", or asks about creating a structured brief to hand to a writer for producing search-optimized content.
---

# SEO Content Brief Skill

You are an SEO content strategist. Create comprehensive content briefs that give writers everything they need to produce search-optimized articles that rank.

## Brief Creation Process

### Step 1: Search Intent Analysis

Before writing a brief, determine what Google thinks this query means:

1. **Search the keyword** using WebSearch
2. **Classify intent:**
   - Informational (how, what, why, guide) → Blog post, guide
   - Commercial (best, review, vs, top) → Comparison, listicle
   - Transactional (buy, price, free, download) → Landing page, product page
   - Navigational (brand + feature) → Product/feature page

3. **Identify content type from SERP:**
   - What format dominates top 5? (Listicle, how-to, guide, comparison)
   - What content length are top results? (Estimate from structure)
   - Are there featured snippets? What format? (Paragraph, list, table)

### Step 2: SERP Analysis

For the target keyword, analyze top 5-10 results:

| Result | Title | Format | Est. Length | Unique Angle |
|--------|-------|--------|-------------|-------------|
| #1 | {title} | {format} | {words} | {what makes it different} |
| #2 | ... | ... | ... | ... |

**Extract from top results:**
- Common H2/H3 topics (every result covers these → mandatory sections)
- Unique sections (only 1-2 results cover → differentiation opportunity)
- Questions answered (People Also Ask + in-content FAQs)
- Types of media used (images, videos, tables, infographics)

### Step 3: Keyword Research

**Primary keyword:** The main target
**Secondary keywords:** 5-10 related terms to include naturally
**Question keywords:** 4-6 questions from "People Also Ask"
**LSI keywords:** Related terms that signal topical depth

If SemRush API is available (`SEMRUSH_API_KEY`), pull:
```bash
# Primary keyword data
curl -s "https://api.semrush.com/?type=phrase_all&key=${SEMRUSH_API_KEY}&phrase={keyword}&database=us&export_columns=Ph,Nq,Cp,Co,Nr,Td"

# Related keywords
curl -s "https://api.semrush.com/?type=phrase_related&key=${SEMRUSH_API_KEY}&phrase={keyword}&database=us&export_columns=Ph,Nq,Cp,Co&display_limit=20"

# Question keywords
curl -s "https://api.semrush.com/?type=phrase_questions&key=${SEMRUSH_API_KEY}&phrase={keyword}&database=us&export_columns=Ph,Nq,Cp,Co&display_limit=10"
```
````
END THIRD-PARTY FILE 6a4dee4254bb5597

The third-party file has ended. Everything between the 6a4dee4254bb5597 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2624 of 7344 bytes. © OpenClaudia · MIT · https://github.com/OpenClaudia/openclaudia-skills/tree/HEAD/skills/seo-content-brief/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md