seo-content-brief
Skill4 starsChanged 8 months agoMITView on GitHub
Generate comprehensive, SERP-driven content briefs for writers. Analyzes top-ranking competitors, identifies content gaps, specifies structure, word count, keywords, E-E-A-T requirements, AI citation readiness, and schema recommendations. Use when user says "content brief", "writing brief", "content outline", "article brief", or "create brief for".
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
1
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
- Distinctive: line 170
Before delivering a content brief, verify:
“Common” is measured: kept by at least 6 in 10 of the 27 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.
Files
seo-content-brief — SERP-Driven Content Brief Generation
Brief Generation Process
Step 1: SERP Analysis
Analyze top 10 results for the target keyword:
- Fetch SERP results (via WebSearch or SERP API data)
- Identify content patterns across top rankers
- Map SERP features present (AI Overview, Featured Snippet, PAA, Video)
- Determine dominant search intent
Step 2: Competitor Content Analysis
For each top-5 ranking page, extract:
| Element | What to Capture |
| Word count | Total and per-section breakdown |
| Heading structure | H1, H2, H3 hierarchy and topics covered |
| Content format | Lists, tables, images, videos, infographics |
| Unique angles | What differentiates each competitor's approach |
| E-E-A-T signals | Author credentials, sources cited, experience markers |
| Schema used | Article, FAQ, HowTo (deprecated), Product, etc. |
| Internal links | How many, to what types of pages |
| Multimedia | Images count, video embeds, infographics |
Step 3: Content Gap Identification
Compare competitor coverage to find:
- Subtopics ALL top 5 cover → Must include (table stakes)
- Subtopics 2-3 cover → Should include (competitive advantage)
- Subtopics NONE cover → Opportunity for differentiation
- Questions in PAA → Direct answer opportunities
- AI Overview sources → What got cited and why
Step 4: Brief Assembly
Content Brief Template
# Content Brief: [Target Keyword]
## Target
- **Primary Keyword**: [keyword] (search volume: X/mo, difficulty: X)
- **Secondary Keywords**: [3-5 keywords with volume]
- **Search Intent**: [Informational / Commercial / Transactional / Navigational]
- **Target URL**: [new page or existing URL to update]
## SERP Landscape
- **AI Overview present**: Yes/No — [if yes, what sources cited]
- **Featured Snippet**: Yes/No — [type: paragraph/list/table]
- **PAA questions**: [list 4-6 questions]
- **SERP features**: [Video, Image Pack, Local Pack, Shopping, etc.]
- **Dominant content format**: [Guide / Listicle / Comparison / Tutorial]
## Content Specifications
- **Target Word Count**: [X-Y words] (based on competitor avg ±20%)
- **Content Format**: [Long-form guide / Listicle / How-to / Comparison]
- **Reading Level**: [Grade 8-10 for general, Grade 12+ for technical]
- **Tone**: [Authoritative / Conversational / Technical / Educational]
## Required Structure
### H1: [Exact title recommendation]
### Opening (first 200 words):
- Direct answer to the primary query
- Key statistic or fact
- Value proposition for reading further
- Primary keyword in first 60 words
### H2: [Section 1 title]
- Key points to cover
- Data/statistics to include
- [134-167 word self-contained answer block for AI citation]
### H2: [Section 2 title]
- Key points to cover
- Comparison table recommended
- Internal link opportunity: [target page]
### [Continue for all required H2/H3 sections...]
### FAQ Section
- Q: [PAA question 1] — A: [brief answer guidance]
- Q: [PAA question 2] — A: [brief answer guidance]
- Q: [PAA question 3] — A: [brief answer guidance]
## Keyword Integration
- **Primary keyword density**: 0.5-1.5%
- **Keyword placement**: Title, H1, first 100 words, 1-2 H2s, meta description
- **Semantic keywords**: [10-15 LSI terms to weave naturally]
- **Entity mentions**: [related entities to reference]
## E-E-A-T Requirements
### Experience
- [ ] Include first-hand experience signals ("In our testing...", "We found that...")
- [ ] Original data, screenshots, or case study results
- [ ] Process documentation or methodology description
### Expertise
- [ ] Author byline with relevant credentials
- [ ] Technical accuracy verified by subject matter expert
- [ ] Up-to-date with current developments (cite recent sources)
### Authoritativeness
- [ ] Cite 3-5 authoritative external sources
- [ ] Reference industry standards or official documentation
- [ ] Include expert quotes where possible
### Trustworthiness
- [ ] Publication date and last-updated date
- [ ] Clear attribution for all claims
- [ ] Transparent about limitations or caveats
## AI Citation Readiness
- [ ] Self-contained answer blocks (134-167 words) for key questions
- [ ] Clear definition patterns ("X is..." / "X refers to...")
- [ ] Specific statistics with sources (AI systems preferentially cite data)
- [ ] Structured comparison tables (AI extracts tabular data effectively)
- [ ] Question-based H2/H3 headings matching search queries
## Multimedia Requirements
- [ ] Hero image (above fold, relevant to topic)
- [ ] [X] supporting images/diagrams (one per major section minimum)
- [ ] Alt text specifications for each image
- [ ] Video embed recommendation: [Yes/No — if yes, what content]
- [ ] Table/chart for comparative data
## Schema Markup
- **Required**: [Article / BlogPosting / Product / etc.]
- **Recommended**: [BreadcrumbList, Person (author), Organization]
- **Optional**: [VideoObject if video included]
- Do NOT use: HowTo (deprecated), FAQ (restricted to gov/health)
## Internal Linking Plan
- **Link TO this page from**: [3-5 existing pages with anchor text]
- **Link FROM this page to**: [3-5 target pages with anchor text]
- **Pillar page connection**: [parent topic hub if part of cluster]
## Competitive Differentiators
What will make this content BETTER than current top results:
1. [Unique angle / data / perspective competitors lack]
2. [More comprehensive coverage of subtopic X]
3. [Better multimedia / interactive elements]
4. [More recent data / updated information]
5. [Stronger E-E-A-T signals]
## Meta Tags
- **Title**: [50-60 chars, includes primary keyword]
- **Meta Description**: [150-160 chars, compelling, includes keyword]
- **URL Slug**: [short, descriptive, hyphenated]
## Success Metrics
- **Target position**: [#1-3 / top 5 / page 1]
- **Target traffic**: [X organic sessions/month within Y months]
- **AI citation goal**: [Cited in AI Overviews / Featured Snippet capture]
- **Engagement targets**: [Engagement rate >X%, avg time >Y min]Brief Quality Checklist
Before delivering a content brief, verify:
- Word count target is based on competitor analysis (not arbitrary)
- All PAA questions from SERP are addressed
- AI Overview citation strategy is included
- E-E-A-T requirements are specific (not generic)
- Internal linking plan references real existing pages
- Schema recommendation matches page type and is not deprecated
- Competitive differentiators are actionable (not "write better content")
- Success metrics are measurable and realistic
Content Brief Scoring
| Category | Weight | Criteria |
| SERP Alignment | 25% | Brief matches dominant search intent and format |
| Competitive Coverage | 20% | All table-stakes subtopics included + differentiation |
| E-E-A-T Specification | 20% | Specific, actionable E-E-A-T requirements |
| AI Citation Readiness | 15% | Answer blocks, structured data, citation patterns |
| Technical Completeness | 10% | Keywords, schema, meta tags, internal links |
| Actionability | 10% | Writer can execute without additional research |
Content Pipeline (Post-Brief Lifecycle)
The brief is step 1 of a 6-stage content pipeline:
Pipeline Stages
| Stage | Owner | Duration | Deliverable |
| 1. Brief | SEO team | 1-2 days | This content brief |
| 2. Draft | Writer | 3-7 days | First draft following brief |
| 3. Review | SEO + SME | 1-2 days | Fact-check, E-E-A-T verification |
| 4. Optimize | SEO team | 1 day | Keyword placement, schema, meta tags |
| 5. Publish | Content ops | 1 day | Live on site, submitted to GSC |
| 6. Monitor | SEO team | Ongoing | Track performance milestones |
Post-Publish Monitoring Milestones
| Timeframe | Check | Expected | Alert If |
| Day 1-3 | Indexed in GSC | URL appears in index | Not indexed after 3 days |
| Day 7 | Initial ranking | Appears in top 50 | Not ranking at all |
| Day 14 | Ranking trajectory | Climbing steadily | Stuck or declining |
| Day 30 | Stable position | Top 20 target | Still outside top 50 |
| Day 60 | Target achieved | Top 10 for primary KW | Stagnant — trigger content refresh |
Content Refresh Frequency
Prevent content decay with proactive refresh scheduling:
| Content Type | Refresh Cycle | What to Update |
| News/trending | 30 days | Statistics, developments, links |
| Technology | 90 days | Tools, versions, benchmarks |
| Industry guides | 120 days | Data, trends, examples |
| Evergreen | 180 days | Freshness signals, new sections |
| Reference/glossary | 365 days | Definitions, new terms |
Cross-reference: seo-monitor skill for automated content decay detection.
Output
Generate CONTENT-BRIEF-[keyword].md with all sections above filled in.
For batch briefs, generate one file per keyword with consistent formatting.
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 28
- AgriciDaniel/claude-seo★ 20ksame name
- OpenClaudia/openclaudia-skills★ 724same name
- zhtyyx/codex-seo★ 108same name
- whyashthakker/agent-skills-marketing★ 15same name
- prosyo-ai/gtm-skill★ 13same name
- ZachArticulateV/designer-pro-and-seo★ 10same name
- marketingskills/seo★ 7same name
- joaoguirunas/team-os★ 6same name
- avalonreset/legends-seo-dungeon★ 4same name
- creativedeals/free-claude-skill-seo-content-brief★ 4same name
18 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use seo-sxo, seo-google and 9 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.
webdevarifSkillseo-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 10 projects that use this
webdevarifSkillseo-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", or "real CWV data".
Also in 9 projects that use this
Teapot-AgencySkillseo-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
indranilbanerjeeSkillseo-drift
Compare two SEO exports (Search Console, two dates): gainers, losers, drift classes. \"what moved after the core update\"
Also in 9 projects that use this
walternateSkillseo-strategy
Build and execute an SEO strategy for organic search traffic. Use when planning keyword targeting, optimizing content for search engines, building backlinks, improving site structure, or troubleshooting SEO issues. Covers keyword research, on-page SEO, technical SEO basics, link building, and tracking rankings. Trigger on "SEO", "search engine optimization", "rank on Google", "keyword research", "SEO strategy", "organic traffic", "improve search rankings", "SEO for [my site/business]".
Also in 4 projects that use this
- +6 more from webdevarif
In this repository25 other files it gives its agents.
- seo-agentSkill
- seo-auditSkill
- seo-backlinksSkill
- seo-competitor-analysisSkill
- seo-competitor-pagesSkill
- seo-contentSkill
- seo-data-toolsSkill
- seo-geoSkill
- seo-hreflangSkill
- seo-imagesSkill
- seo-keyword-researchSkill
- seo-localSkill
- seo-monitorSkill
- seo-multiplatformSkill
- seo-pageSkill
- seo-performanceSkill
- seo-planSkill
- seo-programmaticSkill
- seo-rank-trackerSkill
- seo-reportSkill
- seo-schemaSkill
- seo-sitemapSkill
- seoSkill
- seo-technicalSkill
- seo-visualSkill
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
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.

