content-brief
About
The content-brief skill provides a structured template and methodology for creating SEO-optimized content briefs. It guides developers through keyword research, SERP analysis, and outline creation to align content with search intent. Use it when preparing writer briefs or planning new content pieces to document SEO requirements.
Quick Install
Claude Code
Recommended/plugin add https://github.com/majiayu000/claude-skill-registrygit clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/content-briefCopy and paste this command in Claude Code to install this skill
Documentation
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)
GitHub Repository
Related Skills
algorithmic-art
MetaThis Claude Skill creates original algorithmic art using p5.js with seeded randomness and interactive parameters. It generates .md files for algorithmic philosophies, plus .html and .js files for interactive generative art implementations. Use it when developers need to create flow fields, particle systems, or other computational art while avoiding copyright issues.
subagent-driven-development
DevelopmentThis skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.
executing-plans
DesignUse the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.
cost-optimization
OtherThis Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.
