seo-content-brief

seo-content-brief is a skill for Claude Code, Codex from OpenClaudia/openclaudia-skills. It costs 62 tokens per session (1,902 once invoked), scanned A, original, MIT.

A skill for creating SEO content briefs: structured plans that tell a writer what to cover in an article designed to appear in search results.

In plain words
What is it for?
Use it to analyze a target keyword, identify search intent and competing result formats, and produce an outline with recommended topics and length.
Why use it?
It helps align an article with what people are searching for and with the formats and topics commonly shown by search engines.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to analyze a target keyword, identify search intent and competing result formats, and produce an outline with recommended topics and length.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/openclaudia/openclaudia-skills/seo-content-brief
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 OpenClaudia/openclaudia-skills --skill seo-content-brief
Clone the repo
git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills

Made for: Claude Code, Codex.

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 seo-content-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/openclaudia/openclaudia-skills/seo-content-brief/github.svg)](https://agentmods.dev/skills/openclaudia/openclaudia-skills/seo-content-brief)
Your own site
<a href="https://agentmods.dev/skills/openclaudia/openclaudia-skills/seo-content-brief"><img src="https://agentmods.dev/badge/skills/openclaudia/openclaudia-skills/seo-content-brief/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 seo-content-brief

Your own site · 80×15
<a href="https://agentmods.dev/skills/openclaudia/openclaudia-skills/seo-content-brief"><img src="https://agentmods.dev/badge/skills/openclaudia/openclaudia-skills/seo-content-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,902 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk warn 16 Feb 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Data Exfiltration · line 53
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 56
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 59
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00062 $0.01902
Opus 5 $0.00031 $0.00951
Sonnet 5 $0.00012 $0.00380
Haiku 4.5 $0.00006 $0.00190

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

Security

Grade A, and why

seo-content-brief scanned grade A with 1 finding 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 13d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

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"
skills/seo-content-brief/SKILL.md · 206 lines

How it starts

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

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:

# 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"

Read the full file on GitHub · 206 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. 13d ago First seen · 206 lines · 62 tokens per session scan A d5dd4e4f1e99

Subscribe to this mod's changes

seo-content-brief is a skill published in the GitHub repository OpenClaudia/openclaudia-skills (689 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 1,902 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens