mcpbeat

Content Brief

nicepkg/ai-workflow-content-brief

Content brief template and creation methodology for SEO-optimized content. Use when preparing briefs for writers or planning new content pieces.

This is a copy. The original lives at nicepkg/content-brief.

926 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
275
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/nicepkg/ai-workflow --skill content-brief

The instruction itself

9 sections, as written by the author

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)

How to use it

Copy the folder

Take nicepkg/ai-workflow-content-brief from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.