agentleFS
nisarthnisarth/claude-skills-store/skills/seo/seo-content-brief/SKILL.md

seo-content-brief

Skill1 starsChanged 7 months agoMITView on GitHub

Build an SEO content brief for a target keyword by analyzing the top 10 SERP results, headings, entities, People Also Ask questions, and competitor word counts. Outputs a structured brief for writers. Trigger with "content brief", "SEO brief for", "brief this keyword", or "write a content brief".

36 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

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 35 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    PAA questions: All visible People Also Ask questions from the SERP.

    line 62
  2. Distinctive:

    Use competitor heading structures as a baseline but encourage original organization.

    line 148
  3. Distinctive:

    Update briefs when SERP results shift significantly.

    line 153

“Common” is measured: kept by at least 6 in 10 of the 35 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

Build a data-driven SEO content brief by analyzing the top 10 SERP results for a target keyword. Extract headings, entities, People Also Ask questions, and competitor benchmarks to guide content creation.

Workflow

Step 1: SERP Analysis

Analyze the current search results for the target keyword:

  • Top 10 results: Title, URL, meta description, content type (blog, product, guide, tool).
  • SERP features: Featured snippets, People Also Ask, knowledge panels, video carousels, image packs.
  • Search intent: Informational, navigational, commercial, or transactional.
  • Content format: Listicle, how-to, comparison, definition, tutorial, case study.
  • Dominant content type: Determine what Google is rewarding for this query.

Step 2: Competitor Content Analysis

Deep-dive into the top-ranking pages:

  • Heading structure: Extract H1, H2, and H3 headings from each top result.
  • Word count: Calculate the range and median word count across the top 10.
  • Key subtopics: Identify sections that appear across multiple competitors.
  • Unique angles: Note differentiated content that only one or two competitors cover.
  • Content freshness: Publication and last-updated dates.
  • Media usage: Images, videos, infographics, interactive elements.

Step 3: Entity and Topic Extraction

Identify the semantic landscape:

  • Primary entities: People, products, concepts, and brands consistently mentioned.
  • Related terms: Semantically related keywords and phrases (LSI concepts).
  • Topic clusters: Subtopics that support topical authority around the main keyword.
  • Missing entities: Concepts the top results cover that any existing page does not.

Step 4: People Also Ask and Related Searches

Capture question-based opportunities:

  • PAA questions: All visible People Also Ask questions from the SERP.
  • Related searches: Bottom-of-SERP suggestions.
  • Autocomplete suggestions: Variations Google suggests while typing the query.
  • Question clustering: Group similar questions to avoid redundancy.

Step 5: Build the Brief

Compile all research into an actionable content brief.

Output Format

## SEO Content Brief: <target keyword>

**Target URL**: <new page or existing URL>
**Search Intent**: Informational / Commercial / Transactional
**Content Format**: <recommended format>
**Target Word Count**: <range based on competitors>
**Difficulty Assessment**: Easy / Medium / Hard

### Search Landscape
- **Monthly search volume**: <volume>
- **SERP features present**: <list>
- **Top competitor domains**: <list>

### Recommended Title
- Option A: <title, 50-60 characters>
- Option B: <title, 50-60 characters>

### Meta Description
<150-160 character meta description with call to action>

### Required Heading Structure

H1: <main heading> H2: <section> H3: <subsection> H2: <section> H3: <subsection> H2: <section> H2: FAQ


### Must-Cover Subtopics
| Subtopic | Competitor Coverage | Priority |
|----------|-------------------|----------|
| <topic> | <X of 10 competitors> | Required |
| <topic> | <X of 10 competitors> | Required |
| <topic> | <X of 10 competitors> | Recommended |

### Key Entities to Include
- <entity 1>
- <entity 2>
- <entity 3>

### People Also Ask (answer in content)
1. <question>
2. <question>
3. <question>
4. <question>

### Internal Linking Targets
- <related page on site> -- anchor: <suggested anchor text>

### Differentiation Angle
<how to make this piece stand out from existing top results>

### Notes for Writer
- <specific guidance on tone, depth, or audience>

Examples

User: "Build a content brief for 'how to migrate from Heroku to AWS'" Action: Analyze top 10 SERP results, extract heading patterns, identify required subtopics (cost comparison, step-by-step, common pitfalls), compile the brief.

User: "Content brief for our existing pricing page targeting 'project management tool pricing'" Action: Analyze competitors, identify missing sections on the current page, recommend additions, and note the commercial intent requiring comparison content.

User: "Quick brief for 'best CRM for small business' -- focus on headings and word count" Action: Pull heading structures from top results, calculate word count benchmarks, provide a streamlined brief.

Best Practices

  • Match the search intent precisely. A transactional keyword needs product-focused content, not a blog post.
  • Use competitor heading structures as a baseline but encourage original organization.
  • Set a word count range, not a fixed target. Quality matters more than length.
  • Include differentiation guidance. Writers need to know why their piece should rank above what already exists.
  • Note which subtopics are required (covered by 7+ of 10 competitors) vs. recommended (covered by 3-6).
  • Provide internal linking targets to strengthen the site's topical authority.
  • Update briefs when SERP results shift significantly. A brief from 6 months ago may be stale.
  • Include PAA questions as FAQ candidates to capture featured snippet opportunities.
  • Specify the target audience and their knowledge level to set the right depth and tone.

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.