SEO Keyword Clustering
AgriciDaniel/claude-seo
Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.
A skill your agent uses when planning a new article. An agent skill from inhouseseo/superseo-skills.
Install Content Brief
$ npx skills add inhouseseo/superseo-skills --skill content-brief -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install inhouseseo/superseo-skills content-brief --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/inhouseseo/superseo-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/content-brief .claude/skills/content-brief && rm -rf skills-srcUse ~/.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/
Install the "content-brief" agent skill from https://github.com/inhouseseo/superseo-skills/tree/main/skills/content-brief into .claude/skills/content-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-brief", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/inhouseseo/superseo-skills/tree/main/skills/content-briefType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add inhouseseo/superseo-skills --skill content-brief -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install inhouseseo/superseo-skills content-brief --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inhouseseo/superseo-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/content-brief .agents/skills/content-brief && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "content-brief" agent skill from https://github.com/inhouseseo/superseo-skills/tree/main/skills/content-brief into .agents/skills/content-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-brief", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add inhouseseo/superseo-skills --skill content-brief -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install inhouseseo/superseo-skills content-brief --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inhouseseo/superseo-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/content-brief .cursor/skills/content-brief && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "content-brief" agent skill from https://github.com/inhouseseo/superseo-skills/tree/main/skills/content-brief into .cursor/skills/content-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-brief", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/inhouseseo/superseo-skills.git --path skills/content-brief--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add inhouseseo/superseo-skills --skill content-brief -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install inhouseseo/superseo-skills content-brief --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inhouseseo/superseo-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/content-brief .gemini/skills/content-brief && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "content-brief" agent skill from https://github.com/inhouseseo/superseo-skills/tree/main/skills/content-brief into .gemini/skills/content-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-brief", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install inhouseseo/superseo-skills content-briefInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add inhouseseo/superseo-skills --skill content-brief -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/inhouseseo/superseo-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/content-brief .github/skills/content-brief && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "content-brief" agent skill from https://github.com/inhouseseo/superseo-skills/tree/main/skills/content-brief into .github/skills/content-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-brief", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add inhouseseo/superseo-skills --skill content-brief -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install inhouseseo/superseo-skills content-brief --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/inhouseseo/superseo-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/content-brief .opencode/skills/content-brief && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "content-brief" agent skill from https://github.com/inhouseseo/superseo-skills/tree/main/skills/content-brief into .opencode/skills/content-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-brief", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
content-brief- GitHub stars
- 352
- Token cost
- ~1.5k tokens
- SKILL.md length
- 790 words
- Files
- 7 (incl. references)
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when planning a new article. An agent skill from inhouseseo/superseo-skills.
- Works in 5 steps: Research the SERP → Identify Search Intent → Map the People Also Ask → …
- Planning a new article
- SKILL.md covers Input, Role, Step 1: Research the SERP and Step 2: Identify Search Intent, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Content Brief is an agent skill from inhouseseo/superseo-skills. Use when planning a new article. The agent Googles the keyword, reads the top 10 results, classifies intent, maps the content gap, and produces a writer-ready brief with structure, outline, and on-page artifacts. No keyword tool required.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/content-types-overview.md`, `references/human-input-framework.md` and `references/information-gain-writing.md`).
It sits in Marketing & SEO, covering Content strategy. The repository describes itself as: 11 Claude skills for SEO: page audits, linkbuilding, article writing, E-E-A-T audits, semantic gap analysis, link building. Methodology from Koray Tuğberk, Kyle Roof, and Lily…. The licence is Apache-2.0.
When your agent uses it
- Planning a new article
- Tasks that involve Content strategy
Example prompts
- “/content-brief”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9cf22cc. 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
Content Brief loads about 1.5k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 63 tokens; SKILL.md has 790 words of instructions outside code blocks.
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 inhouseseo/superseo-skills at commit 9cf22cc, republished under its Apache-2.0 licence (© inhouseseo). 790 words, ~1,510 tokens.
Download SKILL.mdSave it as
.claude/skills/content-brief/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- content-brief
- description
- Use when planning a new article. The agent Googles the keyword, reads the top 10 results, classifies intent, maps the content gap, and produces a writer-ready brief with structure, outline, and on-page artifacts. No keyword tool required.
Content Brief
A writer-ready content brief based on real SERP analysis. The agent Googles the target keyword, reads the top 10 results, classifies intent, identifies competitor gaps, and produces the brief. No keyword tool exports, no manual SERP pasting.
Input
Target keyword (required). Optionally: business context if you want the brief tailored to a specific audience/tone.
If the user didn't provide a keyword, ask for it before proceeding.
Role
You are a senior content strategist and SEO brief specialist with 10+ years of experience. Your job is to produce a complete, writer-ready brief based on what actually ranks right now — not a generic template.
Step 1: Research the SERP
Google the target keyword. Read the top 10 results. For each top-ranking page, note:
- Content format (listicle / long-form guide / comparison / how-to / tool / video)
- Approximate word count
- Heading structure (H1, main H2s)
- Content angle and unique hook
- What they cover that others don't
- Whether they appear to hold a featured snippet, People Also Ask positions, or other SERP features
Base every claim in the brief on pages you actually read. If a result won't fetch, say so and work from the ones you could read — don't infer what an unread page covers.
Step 2: Identify Search Intent
Classify dominant intent: Informational / Commercial Investigation / Transactional / Navigational.
Apply intent-specific length guidance:
- Informational: 1,500–3,000+ words — completeness, PAA coverage
- Commercial: 2,000–4,000 words — features, comparison, objectivity
- Transactional: 800–1,500 words — trust signals, CTAs, specs
- Navigational: 500–1,000 words — speed, direct info
Target word count = average of top 5 results + 10%. Never pad to hit a number.
Step 3: Map the People Also Ask
If PAA questions appear for this keyword, write them down verbatim. They'll become H2/H3 headings in the outline.
Step 4: Identify Content Type
Pick the content type from the SERP pattern. Content types: how-to, definition/explainer, comparison, listicle, product-review, case-study, pillar-page, faq-page, landing-page, service-page, category-page, buying-guide, alternatives-page, pricing-page, location-page.
Load references/content-types-overview.md for the one-screen decision table covering all 23 content types (H1/H2 structure, schema, snippet format, word counts). Use it to pick the right type in 30 seconds, then hand the choice over to write-content.
Step 5: Produce the Brief
Target Keyword Analysis
- Primary keyword | Apparent difficulty based on SERP competition | Dominant intent
- Difficulty strategy: Easy SERP (lots of low-DR competitors, mixed intent) = 3-6 months realistic / Moderate (all top results are DR 40+, uniform intent) = 6-12 months / Hard (top results are all DR 60+, highly optimized, long-form) = 12+ month authority play
- Related terms to target on the same page (from what the top pages cover as H2s)
SERP Competitive Intelligence
For each of the top 3 competitors:
- URL | Estimated words | Format type | Key sections covered | What they miss
Content Gap Analysis
Specific subtopics covered by 2+ top competitors but missing from where most results are thin. Name exact missing sections — not generic "add more depth."
Show full SKILL.md (322 more words)Show less
Recommended Outline
H1 and H2/H3 structure aligned to search intent and the gap analysis. Include:
- Featured snippet target: which H2 hosts the 40-60 word snippet answer — mark the spot
- PAA integration: questions to address as H2/H3 headings
- FAQ section if 3+ PAA questions exist
Hub & Spoke Architecture
- This piece as: hub / spoke / standalone (based on keyword breadth)
- Internal linking pattern recommended
Technical Optimization
- Title tag: 50-60 chars, primary keyword near front
- Meta description: 150-160 chars, intent signal + CTA
- Schema: Article / FAQ / HowTo / Product / Review (choose based on content type)
- Featured snippet format: paragraph (what is) / ordered list (how to) / table (comparison)
E-E-A-T Signals Required
- Author expertise markers needed
- Original data or research to include
- External authoritative sources to cite
Resource Assessment
- Effort: Low (500-1,000w, 2-4h) / Medium (1,000-2,500w, 6-12h) / High (2,500w+, 16h+)
- Realistic 3-month target position given SERP difficulty
What to Ignore
- Keyword density targets — write naturally. Primary keyword in H1, first 100 words, 2-3 H2s (~2% body density is a ceiling, not a target)
- NLP term lists of 50+ words — focus on 5-8 core entities that must appear
- Word count without checking SERP — "write 3,000 words" without intent matching creates padded content
Next Step
Brief ready? Use the write-content skill with this brief as context to write the article.
Bundled references
Load these from references/ only when the step calls for them — don't preload.
content-types-overview.md— decision table for picking the right content type (Step 4)intent-matching.md— deep read on Informational / Commercial / Transactional / Navigational signal matching (Step 2, when the SERP intent is mixed or unclear)serp-driven-writing.md— how to turn the top 10 read into outline decisions (Step 5, if the gap analysis is thin)information-gain-writing.md— what qualifies as "new information" vs. index (Step 5, when briefing the unique angle)structured-data-snippets.md— snippet format per content type (Step 5, "Technical Optimization" block)human-input-framework.md— the 2-3 questions to ask the writer before they start (optional, when briefing for an outside writer rather than the agent)
© inhouseseo, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (references) in skills/content-brief of inhouseseo/superseo-skills.
- SKILL.md
- references/content-types-overview.md
- references/human-input-framework.md
- references/information-gain-writing.md
- references/intent-matching.md
- references/serp-driven-writing.md
- references/structured-data-snippets.md
Open the folder on GitHubat commit 9cf22cc
Compare with similar skills
Content 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Content Brief this skillinhouseseo/superseo-skills | 352 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| SEO Keyword ClusteringAgriciDaniel/claude-seo | 19k | 2 repos | ~3.3k | Automated safety check: Pass | MIT | |
| SEO Content Brief GeneratorAgriciDaniel/claude-seo | 19k | 2 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Getxapi ConnectLeoYeAI/openclaw-marketing-skills | 1k | 1 repos | ~715 | Automated safety check: Pass | Custom licence | |
| Content BriefRyze-AI-Adgent/open-seo-mcp-skills | 4.7k | — | ~610 | Automated safety check: Pass | MIT | |
| Strategic SEO PlanningAgriciDaniel/claude-seo | 19k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
SEO Content Brief Generator
AgriciDaniel/claude-seo
Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.
Getxapi Connect
LeoYeAI/openclaw-marketing-skills
Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.
Content Brief
Ryze-AI-Adgent/open-seo-mcp-skills
SERP-driven content brief for a target keyword — what ranks, what to cover, headings, questions, internal links from your own data.
Strategic SEO Planning
AgriciDaniel/claude-seo
Builds an SEO strategy for a new or existing site: discovery, competitor analysis, site architecture, content plan, technical foundation and a four-phase roadmap.
Blog Cluster
AgriciDaniel/claude-blog
Semantic topic cluster planning and automated execution engine for claude-blog.
More from inhouseseo/superseo-skills
All 11 skills in this repoEeat Audit
inhouseseo/superseo-skills
A skill your agent uses when auditing a page for E-E-A-T signals.
Expert Interview
inhouseseo/superseo-skills
A skill your agent uses when extracting first-party expertise from a subject-matter expert before writing content.
Featured Snippet Optimizer
inhouseseo/superseo-skills
A skill your agent uses when you want to win a featured snippet for a keyword you already rank for.
Improve Content
inhouseseo/superseo-skills
A skill your agent uses when rewriting or refreshing an existing page that's underperforming.
Keyword Deep Dive
inhouseseo/superseo-skills
A skill your agent uses when planning to rank for a specific keyword.
Linkbuilding
inhouseseo/superseo-skills
A skill your agent uses when planning link acquisition. An agent skill from inhouseseo/superseo-skills.
Related
Categories
Questions about Content Brief
What does Content Brief do?
A skill your agent uses when planning a new article. An agent skill from inhouseseo/superseo-skills. Content Brief is an agent skill from inhouseseo/superseo-skills. Use when planning a new article.
When should I use Content Brief?
Content Brief fits situations like: planning a new article; tasks that involve Content strategy.
How do I install Content Brief in Claude Code?
Run `npx skills add inhouseseo/superseo-skills --skill content-brief -a claude-code`. Or copy the skill folder (skills/content-brief in inhouseseo/superseo-skills) into .claude/skills/content-brief in your project. Claude Code loads it when a task matches its description.
How do I install Content Brief in Codex?
Run `npx skills add inhouseseo/superseo-skills --skill content-brief -a codex`. Or copy the skill folder (skills/content-brief in inhouseseo/superseo-skills) into .agents/skills/content-brief in your project. Codex loads it when a task matches its description.
Can I use Content 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 inhouseseo/superseo-skills --skill content-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/content-brief, .gemini/skills/content-brief, .github/skills/content-brief and .opencode/skills/content-brief in your project.
What does Content Brief need to run?
SKILL.md names no scripts, command-line tools or credentials: Content Brief is instructions for the agent only.
Does Content 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 Content 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 Content Brief use?
Content Brief is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Content Brief use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 12k tokens, read only when the agent opens those files.
What are the alternatives to Content Brief?
Skills that share tags, products or a category with Content Brief: SEO Keyword Clustering (AgriciDaniel/claude-seo, 19k stars), SEO Content Brief Generator (AgriciDaniel/claude-seo, 19k stars), Getxapi Connect (LeoYeAI/openclaw-marketing-skills, 1k stars) and Content Brief (Ryze-AI-Adgent/open-seo-mcp-skills, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Content Brief?
inhouseseo (a GitHub user) maintains it in inhouseseo/superseo-skills, which has 352 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 3, 2026.
Source: inhouseseo/superseo-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.