Content brief
Skill nicepkg/ai-workflow/workflows/marketing-pro-workflow/.claude/skills/content-brief
🚀 170+ pre-built skills for Claude Code, Cursor, Codex & 14+ AI tools. Stop re-teaching your AI the same things. One command → instant domain expertise. Marketing, SEO, Trading, Video, PM workflows included.
npx -y skills add nicepkg/ai-workflow --skill content-briefAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Content brief template and creation methodology for SEO-optimized content. Use when preparing briefs for writers or planning new content pieces.
SKILL.md
3.6 KB, 919 tokens by cl100k_base, as published. Nobody here has run it
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)
Gives 0 of the 12 instructions most plan spec skills give in 919 tokens
Counted across 1,100 of the 1,860 authors here whose files we hold, read 2026-08-06
- ask one question at a timein 46 of 1100, across 38 files
- Break plans into vertical slicesin 28 of 1100, across 10 files
- Publish issues in dependency orderin 27 of 1100, across 9 files
- Iterate until user approves the breakdownin 24 of 1100, across 6 files
- Explore the repository to understand the codebase statein 24 of 1100, across 7 files
- Use domain glossary vocabularyin 23 of 1100, across 5 files
- Apply correct triage labels to published issuesin 23 of 1100, across 5 files
- Write failing tests before implementation codein 23 of 1100, across 18 files
- Prefer AFK slices over HITLin 22 of 1100, across 7 files
- ask clarifying questions until requirements are concretein 21 of 1100, across 13 files
- Respect existing architecture decision recordsin 20 of 1100, across 5 files
- write a specification before writing any codein 20 of 1100, across 12 files
Said here and by no other author read
- extract People Also Ask questions
- note the search intent
- find missing competitor topics
- create an outline using header tags
- map keywords to specific sections
- define E-E-A-T requirements
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.