seo-content-brief
SEO content brief creation with keyword research, search intent analysis, and content structure. Covers SERP analysis, heading hierarchy, word count targets, and internal linking strategy. Use for: content briefs, SEO writing, blog strategy, content planning, keyword targeting. Triggers: seo content brief, content brief, seo brief, keyword research, search intent, content strategy, blog brief, seo writing, content planning, keyword targeting, serp analysis, content outline, seo article, blog seo
What this skill does
> **Install the belt CLI skill:** `npx skills add belt-sh/cli`
# SEO Content Brief
Create data-driven content briefs via [inference.sh](https://inference.sh) CLI.
## Quick Start
> Requires inference.sh CLI (`belt`). [Install instructions](https://raw.githubusercontent.com/inference-sh/skills/refs/heads/main/cli-install.md)
```bash
belt login
# Research target keyword
belt app run tavily/search-assistant --input '{
"query": "best project management tools for small teams 2024"
}'
# Analyze top-ranking content
belt app run exa/search --input '{
"query": "project management tools small teams comparison guide"
}'
```
## Content Brief Template
Every brief should answer these questions before writing begins:
```markdown
# Content Brief: [Working Title]
## Target
- **Primary keyword:** [exact keyword]
- **Secondary keywords:** [3-5 related terms]
- **Search intent:** [informational / commercial / transactional / navigational]
- **Target word count:** [X,XXX words]
- **Target URL:** /blog/[slug]
## Search Intent Analysis
- What is the searcher trying to accomplish?
- What format do top results use? (listicle, guide, comparison, tutorial)
- What questions need answering?
## Outline
H1: [Title with primary keyword]
H2: [Section 1]
H3: [Subsection]
H2: [Section 2]
...
## Competitors to Beat
1. [URL] — [word count] — [what they do well] — [gap/weakness]
2. [URL] — [word count] — [what they do well] — [gap/weakness]
3. [URL] — [word count] — [what they do well] — [gap/weakness]
## Unique Angle
What makes this piece different/better than what already ranks?
## Internal Links
- Link TO: [existing pages to link to from this article]
- Link FROM: [existing pages that should link to this new article]
```
## Search Intent Types
| Intent | What Searcher Wants | Content Format | Example Query |
|--------|-------------------|----------------|--------------|
| **Informational** | Learn something | Guide, tutorial, explainer | "what is CI/CD" |
| **Commercial** | Compare before buying | Comparison, listicle, review | "best CI/CD tools 2024" |
| **Transactional** | Buy/sign up | Product page, pricing page | "GitHub Actions pricing" |
| **Navigational** | Find a specific page | — (don't target these) | "GitHub login" |
**Match format to intent.** If top 10 results are all listicles, write a listicle. If they're all tutorials, write a tutorial. Fighting the SERP format loses.
## SERP Analysis Process
```bash
# Step 1: See what currently ranks
belt app run tavily/search-assistant --input '{
"query": "[your target keyword]"
}'
# Step 2: Analyze top-ranking content
belt app run tavily/extract --input '{
"urls": ["https://top-result-1.com/article", "https://top-result-2.com/article"]
}'
# Step 3: Find related questions (People Also Ask)
belt app run tavily/search-assistant --input '{
"query": "[keyword] questions people ask FAQ"
}'
# Step 4: Find content gaps
belt app run exa/search --input '{
"query": "[keyword] [subtopic competitors miss]"
}'
```
### What to Extract from Top Results
| Data Point | Why |
|-----------|-----|
| **Word count** | Sets your minimum (match or exceed top 3) |
| **Heading structure** | Shows what Google considers complete coverage |
| **Topics covered** | Every topic they cover, you must cover |
| **Topics missed** | Your opportunity to be more comprehensive |
| **Content format** | Listicle, guide, tutorial, comparison |
| **Media used** | Images, videos, tables, infographics |
| **Internal/external links** | Reference quality signals |
## Keyword Research
### Keyword Metrics
| Metric | What It Means | Target |
|--------|--------------|--------|
| **Search volume** | Monthly searches | Depends on niche (100+ for long-tail) |
| **Keyword difficulty** | Competition level | < 30 for new sites, < 50 for established |
| **CPC** | What advertisers pay | Higher CPC = more commercial value |
| **Search intent** | What users want | Must match your content type |
### Finding Keywords
```bash
# Seed keyword research
belt app run tavily/search-assistant --input '{
"query": "project management software long tail keywords related searches"
}'
# Find question-based keywords
belt app run exa/search --input '{
"query": "questions about project management tools for startups"
}'
# Competitor keyword analysis
belt app run tavily/search-assistant --input '{
"query": "site:competitor.com/blog top performing pages topics"
}'
```
### Keyword Clustering
Group related keywords into one piece of content:
```
Primary: "best project management tools for small teams"
Cluster:
- "project management software small business"
- "project management tools comparison"
- "simple project management app"
- "project management for startups"
- "affordable project management software"
```
**One page per keyword cluster.** Don't create separate pages for each variation — that's keyword cannibalization.
## Heading Structure
### Rules
| Rule | Why |
|------|-----|
| One H1 per page | SEO standard, contains primary keyword |
| H2s = main sections | Each should target a secondary keyword or question |
| H3s = subsections | Break up long H2 sections |
| Primary keyword in H1 | Direct ranking signal |
| Secondary keywords in H2s | Topical coverage signal |
| Question format for some H2s | Targets "People Also Ask" |
| Logical hierarchy | Never skip levels (H1 → H3 without H2) |
### Example Structure
```
H1: Best Project Management Tools for Small Teams (2025)
H2: How We Evaluated These Tools
H2: Top 10 Project Management Tools Compared
H3: 1. Tool A — Best for [use case]
H3: 2. Tool B — Best for [use case]
...
H2: Feature Comparison Table
H2: How to Choose the Right Tool for Your Team
H3: Team Size Considerations
H3: Budget Considerations
H2: Frequently Asked Questions
H3: What is the easiest project management tool?
H3: Do small teams need project management software?
H2: Conclusion
```
## Word Count Targets
| Content Type | Word Count | When |
|-------------|-----------|------|
| Short-form blog | 800-1,200 | News, updates, opinions |
| Standard blog | 1,500-2,000 | How-tos, tutorials |
| Long-form guide | 2,500-4,000 | Comprehensive guides, comparisons |
| Pillar content | 4,000-7,000 | Definitive guides, hub pages |
| Glossary/definition | 300-800 | Quick reference terms |
**Rule: match or exceed the average word count of the top 3 ranking results.** Don't pad — every word should add value.
## On-Page SEO Checklist
| Element | Rule |
|---------|------|
| **Title tag** | Primary keyword + compelling hook, 50-60 characters |
| **Meta description** | Includes keyword, 150-160 characters, includes CTA |
| **URL slug** | Short, keyword-rich: `/best-project-management-tools` |
| **H1** | Primary keyword, matches search intent |
| **First 100 words** | Include primary keyword naturally |
| **Image alt text** | Descriptive, includes keyword where natural |
| **Internal links** | 3-5 links to related content |
| **External links** | 2-3 authoritative sources |
| **Schema markup** | FAQ, HowTo, or Article schema where applicable |
## Content Differentiation
### Unique Angles
| Angle | Example |
|-------|---------|
| **Original data** | "We surveyed 500 PMs — here's what they use" |
| **Expert quotes** | Interview practitioners for original insights |
| **Real examples** | Screenshots, case studies, not just descriptions |
| **More comprehensive** | Cover subtopics competitors skip |
| **More current** | Updated data, newer tools, recent changes |
| **Better visuals** | Comparison tables, infographics, decision trees |
```bash
# Generate comparison infographic
belt app run infsh/html-to-image --input '{
"html": "<div style=\"width:1200px;height:800px;background:white;padding:40px;font-family:system-ui\"><h2 style=\"font-size:28px;color:#1e293b;text-align:center;margin-bottom:30px\">Project Management Tools Comparison</h2><table style=\"width:100%;border-collapse:collapse;font-sRelated 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".