content-brief
Content brief template and creation methodology for SEO-optimized content. Use when preparing briefs for writers or planning new content pieces.
What this skill does
plugin: seo
updated: 2026-01-20
# Content Brief
## When to Use
- Preparing briefs for content writers
- Planning new content pieces
- Documenting SEO requirements for articles
- Aligning content with keyword research
## Brief Creation Methodology
### Step 1: Keyword Research
1. Identify primary keyword (highest priority)
2. Identify 3-5 secondary keywords
3. Extract People Also Ask questions
4. Note search intent (informational/commercial/transactional)
### Step 2: SERP Analysis
1. Analyze top 10 ranking pages
2. Note average word count
3. Identify common content format (listicle, guide, etc.)
4. Find content gaps (topics competitors miss)
### Step 3: Outline Creation
1. Create H1 with primary keyword
2. Plan H2s to cover required topics
3. Plan H3s for detailed sections
4. Map keywords to specific sections
### Step 4: Requirements Definition
1. Set word count target (based on competitors + 20%)
2. Define E-E-A-T requirements
3. Specify internal linking targets
4. Set readability target (Flesch 60-70)
## Brief Template
```markdown
---
plugin: seo
updated: 2026-01-20
type: content-brief
created_by: {agent_or_command}
created_at: {timestamp}
keyword: "{keyword}"
session_id: {session_id}
session_path: {session_path}
status: complete
---
plugin: seo
updated: 2026-01-20
# Content Brief: {Title}
## Target Keyword
- **Primary**: {keyword}
- **Secondary**: {keyword2}, {keyword3}, {keyword4}
- **Questions to Answer**:
1. {PAA question 1}
2. {PAA question 2}
3. {PAA question 3}
## Search Intent
- **Type**: Informational | Commercial | Transactional
- **User Goal**: {what user wants to accomplish}
## Content Specifications
- **Word Count**: {min}-{max} words
- **Format**: {article, listicle, guide, comparison}
- **Tone**: {professional, conversational, technical}
- **Target Audience**: {description}
## Required Sections
1. **{H2: Section topic}** - {brief description of what to cover}
2. **{H2: Section topic}** - {brief description}
3. **{H2: Section topic}** - {brief description}
4. **{H2: Section topic}** - {brief description}
## Featured Snippet Opportunity
- **Type**: {paragraph, list, table}
- **Target Query**: {question to answer}
- **Format**: {how to structure the answer}
## Competitor Analysis
| Competitor | Word Count | Unique Angle | Gap |
|------------|------------|--------------|-----|
| {site1} | {count} | {angle} | {what they miss} |
| {site2} | {count} | {angle} | {what they miss} |
| {site3} | {count} | {angle} | {what they miss} |
## E-E-A-T Requirements
- **Experience**: {specific examples to include from first-hand experience}
- **Expertise**: {depth of coverage required, technical accuracy needs}
- **Authority**: {sources to cite, data to include}
- **Trust**: {claims to verify, transparency requirements}
## Internal Linking
- Link to: {list of existing content to link}
- Anchor text suggestions: {list}
## SEO Requirements Checklist
- [ ] Keyword in title and H1
- [ ] Keyword in first 100 words
- [ ] 1-2% keyword density
- [ ] Minimum 3 internal links
- [ ] At least 1 external authoritative link
- [ ] Meta title: 50-60 characters
- [ ] Meta description: 150-160 characters with CTA
- [ ] Flesch Reading Ease: 60-70
```
## Quality Checklist
Before finalizing a brief, verify:
- [ ] Primary keyword clearly defined
- [ ] Search intent identified and explained
- [ ] Word count based on competitor analysis
- [ ] All PAA questions captured
- [ ] Required sections cover all topics
- [ ] E-E-A-T requirements specific and actionable
- [ ] Internal linking targets identified
- [ ] Featured snippet opportunity noted (if any)
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".