seo-content
Use this skill when the user needs to write SEO content — blog posts, landing pages, feature pages, comparison pages, how-to guides, or any content meant to rank in search and get cited by AI. Covers content briefs, humanized writing that avoids AI detection, SERP feature targeting, entity optimization, content refresh, and quality self-checks. This is the writing skill — for strategy see seo, for technical implementation see technical-seo, for auditing see seo-audit.
What this skill does
# SEO Content Generation
You write SEO content that ranks in Google, gets cited by AI search engines, and reads like a sharp human wrote it — because the fastest way to get penalized or ignored is to publish content that smells like AI.
This skill covers the full content production workflow: brief the piece, write it with humanization baked in, optimize for SERP features and AI citations, then self-check before delivery.
For content strategy and keyword research, see **seo**. For technical implementation (schema, meta tags, CWV), see **technical-seo**. For auditing an existing site, see **seo-audit**.
---
## The Workflow
Every piece of content follows this sequence:
1. **Brief** — Research the keyword, analyze the SERP, find the angle
2. **Write** — Draft with humanization rules applied from the start (not bolted on after)
3. **Optimize** — Target SERP features, structure for AI citation, handle entity SEO
4. **Check** — Run the quality self-check before delivering
Never skip the brief. Writing without a brief produces generic content that ranks nowhere.
---
## Step 1: Content Brief
Before writing a single word, produce a brief. This is the most important step — it determines whether the content has a reason to exist.
### Brief Template
```
## Content Brief: [Working Title]
**Target keyword:** [primary keyword]
**Secondary keywords:** [3-5 related terms to include naturally]
**Search intent:** [informational / commercial / transactional]
**Monthly search volume:** [if known, or estimate as low/medium/high]
**SERP analysis:**
- What currently ranks: [describe the top 3-5 results — format, length, angle]
- What's missing: [the gap you'll fill — what do all top results fail to cover?]
- SERP features present: [featured snippet? PAA? video carousel? AI overview?]
**Content angle:** [your unique take — why should THIS piece exist when 10 others already do?]
Angle types: original data, first-person experience, contrarian position,
deeper expertise, newer information, better structure, specific audience focus
**Content type:** [how-to / comparison / listicle / guide / landing page / case study]
**Target word count:** [based on what's ranking — match or beat by 20%]
**Outline:**
- H1: [title — keyword-front-loaded, compelling]
- H2: [section] — targets [SERP feature or PAA question]
- H3: [subsection]
- H2: [section]
...
**Internal links:** [2-3 existing pages to link TO from this content]
**Link TO this from:** [1-2 existing pages that should link to this new piece]
**CTA placement:** [where and what — e.g., "inline CTA after section 3 → free trial"]
**Featured snippet target:** [the specific query + format: paragraph/list/table]
**AI citation target:** [the specific question this content should be cited for]
```
### Finding the Angle
The angle is everything. Without one, you're writing content that already exists.
| Angle Type | When to Use | Example |
|-----------|-------------|---------|
| **Original data** | You have data nobody else does | "We analyzed 2,847 SaaS pricing pages. Here's what converts." |
| **First-person experience** | You've actually done the thing | "I migrated 3 production apps from Heroku to Railway. Here's what broke." |
| **Contrarian position** | The consensus is wrong or incomplete | "Stop obsessing over domain authority. Here's what actually moves rankings." |
| **Deeper expertise** | Top results are shallow | "Every guide says 'use schema markup.' None show you the 6 schemas that actually trigger rich results." |
| **Newer information** | Top results are outdated | "Google's March 2026 update changed everything about [topic]. Here's what works now." |
| **Specific audience** | Top results are generic | "CI/CD for solo developers — not the enterprise playbook, the one-person-team playbook." |
**If you can't articulate the angle, don't write the piece.** You'll produce another mediocre article that fights for position 11.
---
## Step 2: Write with Humanization
This is the core of the skill. The humanization rules are not a post-processing step — they're how you write from the first sentence.
For the full humanization framework and anti-detection patterns, see [HUMANIZATION.md](HUMANIZATION.md).
For writing templates by content type, see [CONTENT-TYPES.md](CONTENT-TYPES.md).
### The Non-Negotiable Rules
These apply to every piece of content:
**1. Vary your rhythm.**
Mix sentence lengths aggressively. Some sentences are three words. Others stretch to thirty, with embedded clauses and asides that give the reader a sense of a mind actually thinking through the problem rather than outputting pre-formed paragraphs.
**2. Have a point of view.**
Take positions. "This approach is wrong and here's why" is more valuable than "there are pros and cons to consider." Humans have opinions. AI hedges.
**3. Use first-person experience.**
"I tested this" beats "testing reveals." "We found that" beats "research shows." If you don't have personal experience to draw from, use the founder's — ask them what they've seen, done, or learned.
**4. Be specific, not comprehensive.**
"Vercel deploys in 8 seconds on a cold start" beats "modern hosting platforms offer fast deployment times." Name the tool. Cite the number. Date the experience.
**5. Write ugly sentences on purpose.**
Not every sentence should parse cleanly. Start some with "And" or "But." Use fragments. Interrupt yourself with a dash — then finish the thought. This is how humans actually write when they're not trying to impress an English teacher.
**6. Kill the AI tells.**
No "In today's fast-paced world." No "It's important to note." No "Let's dive in." No "In conclusion." No "Whether you're a beginner or an expert." These are the fingerprints of machine-generated text. See [HUMANIZATION.md](HUMANIZATION.md) for the complete list.
**7. Front-load the answer.**
The first 1-2 sentences of every section should directly answer the question the heading asks. Then elaborate. This serves both featured snippets and AI citations.
**8. Earn every paragraph.**
If a paragraph restates what the previous one said, delete it. If a section summarizes the article so far, delete it. Humans don't recap themselves every 300 words.
---
## Step 3: Optimize
After the draft exists, optimize for discoverability.
### SERP Feature Targeting
Different SERP features require different content structures:
**Featured Snippet (paragraph):**
- Trigger: question-based query ("what is...", "how does...")
- Format: answer the question in 40-60 words immediately after the H2/H3
- The answer must be self-contained — it should make sense without the surrounding text
**Featured Snippet (list):**
- Trigger: "how to...", "steps to...", "best..." queries
- Format: numbered or bulleted list with 5-8 items, each 1 line
- Use an H2 that matches the query, immediately followed by the list
**Featured Snippet (table):**
- Trigger: comparison queries, "vs", pricing, specs
- Format: HTML table with clear column headers
- Keep to 3-5 columns, 4-8 rows
**People Also Ask (PAA):**
- Use PAA questions as H2 or H3 headings verbatim
- Answer in the first 1-2 sentences (50-80 words), then elaborate
- Include 3-5 PAA-style question headings per article
- Find real PAA questions by searching your target keyword in Google
**AI Overviews / AI Citations:**
- Lead with citable facts: "[Thing] is [definition/claim]. According to [source], [statistic]."
- Include statistics with source and year: "53% of web traffic comes from organic search (BrightEdge, 2025)"
- Use FAQ schema on question-answer pairs (see technical-seo skill)
- Add TL;DR blocks that can be extracted as standalone answers
### Entity & Semantic Optimization
Google and AI models understand content through entities, not just keywords.
**Entity rules:**
- **Define entities on first mention.** "INP (Interaction to Next Paint) is a Core Web Vital that measures how quickly a page responds to user interactions." Don't assume the reader (or tRelated 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".