Content brief template and creation methodology for SEO-optimized content. Use when preparing briefs for writers or planning new content pieces.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
name: content-brief description: Content brief template and creation methodology for SEO-optimized content. Use when preparing briefs for writers or planning new content pieces.
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
- Identify primary keyword (highest priority)
- Identify 3-5 secondary keywords
- Extract People Also Ask questions
- Note search intent (informational/commercial/transactional)
Step 2: SERP Analysis
- Analyze top 10 ranking pages
- Note average word count
- Identify common content format (listicle, guide, etc.)
- Find content gaps (topics competitors miss)
Step 3: Outline Creation
- Create H1 with primary keyword
- Plan H2s to cover required topics
- Plan H3s for detailed sections
- Map keywords to specific sections
Step 4: Requirements Definition
- Set word count target (based on competitors + 20%)
- Define E-E-A-T requirements
- Specify internal linking targets
- Set readability target (Flesch 60-70)
Brief Template
---
type: content-brief
created_by: {agent_or_command}
created_at: {timestamp}
keyword: "{keyword}"
session_id: {session_id}
session_path: {session_path}
status: complete
---
# 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)
More by MadAppGang
View allChoose optimal external AI models for code analysis, bug investigation, and architectural decisions. Use when consulting multiple LLMs via claudish, comparing model perspectives, or investigating complex Go/LSP/transpiler issues. Provides empirically validated model rankings (91/100 for MiniMax M2, 83/100 for Grok Code Fast) and proven consultation strategies based on real-world testing.
CRITICAL - Guide for using Claudish CLI ONLY through sub-agents to run Claude Code with OpenRouter models (Grok, GPT-5, Gemini, MiniMax). NEVER run Claudish directly in main context unless user explicitly requests it. Use when user mentions external AI models, Claudish, OpenRouter, or alternative models. Includes mandatory sub-agent delegation patterns, agent selection guide, file-based instructions, and strict rules to prevent context window pollution.
MANDATORY tracking protocol for multi-model validation. Creates structured tracking tables BEFORE launching models, tracks progress during execution, and ensures complete results presentation. Use when running 2+ external AI models in parallel. Trigger keywords - "multi-model", "parallel review", "external models", "consensus", "model tracking".
XML tag structure patterns for Claude Code agents and commands. Use when designing or implementing agents to ensure proper XML structure following Anthropic best practices.