agentleFS
OpenClaudiaOpenClaudia/openclaudia-skills/skills/seo-content-brief/SKILL.md

seo-content-brief

Skill731 starsChanged 5 months agoMITView on GitHub

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.

  • Reads credentials

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-sxo, seo-google and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • timruebenachSkill

    seo-sxo

    Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".

    Also in 12 projects that use this

  • timruebenachSkill

    seo-google

    Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", "google api setup", "real CWV data", "impressions", "clicks", "CTR", "position data", "LCP", "INP", "CLS", "FCP", "TTFB", or "Lighthouse scores".

    Also in 11 projects that use this

  • indranilbanerjeeSkill

    seo-drift

    Compare two SEO exports (Search Console, two dates): gainers, losers, drift classes. \"what moved after the core update\"

    Also in 11 projects that use this

  • amirjahfar1Skill

    seo-firecrawl

    Ad-hoc web scraping, site mapping, and full-site crawling via Firecrawl MCP. Returns raw HTML, parsed metadata (og:*, twitter:*, JSON-LD, canonical, robots), JS-rendered DOM, and screenshots that WebFetch cannot. Distinct from the DataForSEO skills (which give keyword/traffic/SERP data) and from WebFetch (which gives markdown prose only). Use when the user says "scrape this page", "crawl this site", "map this site", "find all pages on", "get the OG tags", "get the JSON-LD", "render this JS-heavy page", or any task where raw `<head>` metadata, structured-data scripts, or post-JS DOM are the actual deliverable. Also invoked as a sub-step from other skills that need raw HTML.

    Also in 3 projects that use this

  • Teapot-AgencySkill

    seo-internal-linking

    AI-powered internal linking recommendations z brief + site map. Reads brief.json (z $seo-content-brief) + site_map.json (z $seo-site-crawler), AI-skóruje candidate URLs by semantic relevance to brief topic + secondary KWs, outputs ranked top 5-10 s anchor suggestions a reasoning. Auto-fired počas $seo-content-brief Section 7. Triggers - "navrhni internal linky pre brief XYZ", "internal linking pre <slug>", "linking suggestions pre brief". Pre site URL discovery (zdroj data) use $seo-site-crawler. Pre brief generation use $seo-content-brief.

    Also in 3 projects that use this

  • AgriciDanielSkill

    seo-agentic

    Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).

    Also in 3 projects that use this

  • +6 more from timruebenach

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 30 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 14
  2. Very specific:

    If SemRush API is available (SEMRUSH_API_KEY), pull:

    line 50
  3. Distinctive:

    No skipped levels (H1 → H3 without H2)

    line 82
  4. Distinctive:

    Always verify keyword data is current.

    line 203
  5. Distinctive:

    If the SERP is dominated by highly authoritative sites (Wikipedia, government sites, major publications), note this in the brief — the …

    line 204

“Common” is measured: kept by at least 6 in 10 of the 30 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

ResultTitleFormatEst. LengthUnique 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"

Step 4: Build the Heading Structure

Map out the exact heading structure:

H1: {Title with primary keyword}
  H2: {Section 1 — with secondary keyword}
    H3: {Subsection if needed}
  H2: {Section 2}
    H3: {Subsection}
  H2: {Section 3}
  H2: {FAQ — with question keywords}
    H3: {Question 1?}
    H3: {Question 2?}

Heading rules:

  • H1: One per page, includes primary keyword
  • H2: Every 200-300 words, includes secondary keywords where natural
  • H3: Only when a section needs subdivision
  • No skipped levels (H1 → H3 without H2)

Step 5: Content Differentiation

What will make this article better than the current #1 result?

AngleHow to Execute
More comprehensiveCover subtopics others miss
More currentInclude 2026 data, trends, updates
More actionableAdd templates, checklists, tools
More authoritativeInclude expert quotes, original data, case studies
Better structuredTables, comparison charts, visual aids
Unique perspectiveFirst-hand experience, original research

Brief Output Format

# Content Brief: {Primary Keyword}

**Date:** {date}
**Author:** {assigned writer or TBD}
**Due date:** {if applicable}

---

## Target Keyword Data

| Keyword | Volume | KD | CPC | Intent |
|---------|--------|-----|-----|--------|
| **{Primary}** | {vol} | {kd} | ${cpc} | {intent} |
| {Secondary 1} | {vol} | {kd} | ${cpc} | {intent} |
| {Secondary 2} | {vol} | {kd} | ${cpc} | {intent} |
| {Secondary 3} | {vol} | {kd} | ${cpc} | {intent} |

## Content Specifications

| Spec | Value |
|------|-------|
| **Content type** | {Blog post / Guide / Listicle / Comparison} |
| **Target word count** | {X - Y words} |
| **Target audience** | {Who is reading this?} |
| **Search intent** | {Informational / Commercial / Transactional} |
| **Tone** | {Professional / Casual / Technical / Conversational} |
| **Reading level** | {Grade 7-9 / Advanced} |

## SEO Requirements

- **Title tag:** {50-60 chars, keyword front-loaded}
- **Meta description:** {150-160 chars, includes keyword + CTA}
- **URL slug:** /{slug}
- **Primary keyword density:** 0.5-1.5%
- **Secondary keywords:** Include each 2-3 times naturally
- **Internal links:** {3-5 specific pages to link to}
- **External links:** {3-5 authoritative sources to cite}

## Heading Structure

{Full H1-H3 outline as designed in Step 4}


## Section-by-Section Guidance

### {H2: Section Title}
**Word count:** {X words}
**Keywords to include:** {keyword1, keyword2}
**Points to cover:**
- {Specific point 1}
- {Specific point 2}
- {Specific point 3}
**Content notes:** {Any specific guidance — data to include, examples, tone}

{Repeat for each H2 section}

## FAQ Section (Target Featured Snippets)

| Question | Answer Guidance | Target Keyword |
|----------|----------------|----------------|
| {Question 1?} | {What the answer should cover in 2-4 sentences} | {keyword} |
| {Question 2?} | {Answer guidance} | {keyword} |
| {Question 3?} | {Answer guidance} | {keyword} |

## Visual Content Requirements

| Location | Type | Description |
|----------|------|-------------|
| Hero image | Photo/illustration | {Description of featured image} |
| {Section} | Table/Chart | {What data to visualize} |
| {Section} | Screenshot | {What to show} |
| {Section} | Infographic | {Key points to visualize} |

## Competitive Differentiation

**What makes this better than current top results:**
1. {Specific advantage 1}
2. {Specific advantage 2}
3. {Specific advantage 3}

## Reference Links

- {URL 1}: {What to reference from this}
- {URL 2}: {What to reference from this}

## Checklist for Writer

- [ ] Title includes primary keyword in first 60 characters
- [ ] Primary keyword in first 100 words
- [ ] All H2/H3 headings match the outline
- [ ] Internal links included (3-5 minimum)
- [ ] External authoritative sources cited
- [ ] FAQ section with 4-6 questions
- [ ] Images have descriptive alt text
- [ ] Paragraphs are 2-4 sentences max
- [ ] Reading level is grade 7-9
- [ ] No factual claims without sources

Important Notes

  • A brief should save the writer time, not constrain them. Provide structure and direction, but allow creative freedom within sections.
  • Always verify keyword data is current. Search volumes and difficulty change over time.
  • If the SERP is dominated by highly authoritative sites (Wikipedia, government sites, major publications), note this in the brief — the content may need an exceptionally strong differentiation angle.
  • The heading structure should feel natural to read, not forced for SEO. If a keyword doesn't fit naturally in a heading, use it in the body instead.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.