content-production
Full content production pipeline from blank page to publish-ready piece. Covers competitive research, content briefs, drafting, SEO optimization, readability scoring, editorial quality gates, and internal linking. Use when writing blog posts, articles, guides, or long-form content end-to-end, or when user mentions write a post, draft an article, create content, content pipeline, editorial workflow, content operations, content calendar management, repurposing, or content at scale.
What this skill does
# Content Production The execution engine for content — taking topics from blank page to published, optimized, and distributed. --- ## Table of Contents - [Keywords](#keywords) - [Quick Start](#quick-start) - [Core Workflows](#core-workflows) - [Content Brief Framework](#content-brief-framework) - [Drafting Methodology](#drafting-methodology) - [Optimization Pipeline](#optimization-pipeline) - [Editorial Calendar Management](#editorial-calendar-management) - [Content Repurposing System](#content-repurposing-system) - [Quality Gates](#quality-gates) - [Best Practices](#best-practices) - [Integration Points](#integration-points) --- ## Keywords content production, blog writing, article drafting, content pipeline, editorial workflow, content operations, content calendar, content brief, SEO content, content optimization, readability, internal linking, meta tags, content repurposing, content at scale, editorial calendar, content quality, publishing workflow, long-form content, content management --- ## Quick Start ### Write a Blog Post End-to-End 1. Research: analyze top 5 ranking pieces for the target keyword 2. Brief: define keyword targets, angle, audience, and H2 structure 3. Draft: write with outline-first approach, leading each section with its main point 4. Optimize: SEO pass, readability pass, structure audit, meta tags 5. Validate: run the quality gate checklist before publishing ### Set Up Content Operations 1. Define content pillars aligned with business goals 2. Build an editorial calendar with 4-6 weeks of planned content 3. Establish the production workflow (brief > draft > edit > optimize > publish) 4. Set up repurposing workflow to multiply each piece across channels 5. Define quality gates that every piece must pass before publishing --- ## Core Workflows ### Workflow 1: Research and Brief **Step 1: Competitive Content Analysis** Before writing, understand what already ranks for your target keyword: 1. Identify the top 5-10 ranking pieces 2. Map their angles and formats: | URL | Format | Word Count | Key Angle | What's Missing | |-----|--------|-----------|-----------|----------------| | [URL 1] | How-to guide | 2,400 | Step-by-step technical | No real-world examples | | [URL 2] | Listicle | 1,800 | Tools comparison | Outdated, 2023 data | | [URL 3] | Expert roundup | 3,100 | Multiple perspectives | No actionable framework | 3. Identify the content gap: what does nobody cover well? 4. Verify search intent: | SERP Pattern | Intent | What to Write | |-------------|--------|---------------| | "What is / How to" dominate | Informational | Comprehensive guide or explainer | | Product pages, reviews | Commercial | Comparison or buyer's guide | | Forum results (Reddit, Quora) | Discovery | Opinionated piece with real perspective | | News, recent articles | Trending | Timely take with unique angle | **Step 2: Source Gathering** Collect 3-5 credible, citable sources before drafting: - Original research (studies, surveys, published reports) - Official documentation or industry standards - Expert quotes with full attribution - Data with specific numbers (not vague claims) Rule: If you cannot cite a specific number, do not make a vague claim. **Step 3: Produce the Content Brief** ```markdown ## Content Brief ### Target - Primary keyword: [keyword] (volume: [X], difficulty: [X]) - Secondary keywords: [keyword 1], [keyword 2], [keyword 3] - Search intent: [Informational / Commercial / Transactional] ### Audience - Reader profile: [Who they are and what they know] - Job-to-be-done: [What problem they are solving right now] - Awareness level: [Unaware / Problem-aware / Solution-aware] ### Angle - Unique perspective: [What makes this piece different] - Core argument: [The single thesis of this piece] - Key claims to prove: [3-5 specific claims with supporting evidence] ### Structure - H1: [Working title] - H2: [Section 1] - H2: [Section 2] - H2: [Section 3] - H2: [Section 4] - H2: [Conclusion / Next Steps] ### Requirements - Target word count: [X] - Internal links to include: [List existing pages to link to] - Competitive pieces to beat: [Top 3 URLs to outperform] - CTA: [What action should the reader take] ``` ### Workflow 2: Drafting **Step 1: Build the Outline** Before writing prose, create the header skeleton: - H1 that includes the keyword and creates curiosity - 4-7 H2 sections in logical progression - H3s only when a section genuinely needs subdivision - Conclusion with CTA **Step 2: Write the Introduction** The intro has one job: make the reader believe this piece answers their question. Formula: 1. Name the problem or situation the reader is in (1 sentence) 2. Name what this piece does about it (1 sentence) 3. Establish credibility if relevant (1 sentence, optional) What to avoid: - "In today's digital landscape..." (everyone does this) - Starting with a question unless it is genuinely sharp - Three sentences of context before reaching the point **Step 3: Write Section by Section** For each H2: 1. State the main point in the first sentence 2. Prove it with an example, statistic, or comparison 3. Provide one actionable takeaway before moving to the next section 4. Use transitional phrases to connect sections naturally **Step 4: Write the Conclusion** Three elements: 1. Summary of core argument (1-2 sentences, not a repeat of the intro) 2. The single most important next step 3. CTA aligned with the content goal ### Workflow 3: Optimization Pipeline Run these passes in order on every draft: **Pass 1: SEO Optimization** - [ ] Title tag: contains primary keyword, under 60 characters, curiosity-driving - [ ] H1: different from title tag, keyword-rich, reads naturally - [ ] H2s: at least 2-3 contain secondary keywords or related phrases - [ ] First paragraph: primary keyword appears in first 100 words - [ ] Keyword density: primary keyword appears naturally 3-5 times (not stuffed) - [ ] Image alt text: descriptive, includes keyword where natural - [ ] URL slug: short, keyword-first, no stop words - [ ] Internal links: 2-4 minimum, linking to and from related content - [ ] External links: 1-3 to authoritative sources **Pass 2: Readability** - [ ] Average sentence length: 15-20 words with variation - [ ] No paragraph exceeds 4 sentences - [ ] Active voice used in 80%+ of sentences - [ ] Jargon explained on first use for non-expert audiences - [ ] At least one visual element (image, table, diagram) per 500 words - [ ] Subheadings visible every 200-300 words - [ ] Readability score target: 60-70 (Flesch-Kincaid) **Pass 3: Structure Audit** - [ ] Intro delivers on the headline's promise - [ ] Every H2 earns its place (cut sections that add no value) - [ ] At least 2 concrete examples or illustrations - [ ] Conclusion feels earned, not padded - [ ] Content flow follows logical progression - [ ] No orphan sections that could be merged **Pass 4: Meta Content** - [ ] Meta description: 150-160 characters, includes keyword, ends with hook - [ ] OG title: optimized for social sharing (can differ from meta title) - [ ] OG description: optimized for social click-through - [ ] Canonical URL: set correctly - [ ] Schema markup: Article schema at minimum --- ## Editorial Calendar Management ### Calendar Structure | Week | Monday | Wednesday | Friday | |------|--------|-----------|--------| | 1 | [Pillar topic A] | [Supporting topic B] | [Social repurpose] | | 2 | [Pillar topic C] | [Guest/collab piece] | [Update old post] | | 3 | [Pillar topic A] | [Supporting topic D] | [Social repurpose] | | 4 | [Data/research piece] | [Supporting topic E] | [Roundup/compilation] | ### Content Types by Frequency | Type | Frequency | Purpose | |------|-----------|---------| | Pillar posts (2,000+ words) | 2x/month | Authority building, SEO ranking | | Supporting posts (800-1,500 words) | 2-4x/month | Topic cluster depth, internal linking | | Update/refresh existing posts | 2x/month | Maintain ranking, improve performance | | D
Related 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".