article-content
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
What this skill does
# Content: Article Content Guides creation of **article body content**—the actual text (intro, body, conclusion) for blog posts, guides, and long-form pieces. Focus on **what to write**. For **where it goes** (page structure, schema, metadata), see **article-page-generator**. For short conversion copy (ads, landing pages, CTAs), see **copywriting**. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope - **Article body**: Introduction, body sections, conclusion, CTA - **Content structure**: Hook, QAE pattern, paragraph length, scannability - **Word count**: By article type and search intent - **Writing frameworks**: AIDA, PAS, BAB applied to articles - **GEO elements**: TL;DR, Key Takeaways, answer-first ## Article Types & Word Count (2025) **Quality over length**: Google prioritizes comprehensive coverage of search intent, not word count. Match length to topic depth and intent. | Type | Word count | Use case | |------|------------|----------| | **News / announcements** | 300–600 | Product updates, breaking news, FAQs | | **Short-form** | 500–800 | Landing pages, product pages (scannable) | | **Standard articles / how-tos** | 1,000–1,500 | Single topic; actionable; listicles | | **Listicles** | 1,200–2,000 | "Top 10," "Best X"; numbered lists boost CTR ~70% | | **Cluster articles** | 800–2,500 | Subtopic; links to pillar | | **Pillar / cornerstone** | 2,000–3,500+ | Comprehensive; cluster hub; 6–12 sections | | **Competitive keywords** | 1,800–2,500 | Page-one SEO posts avg ~2,400 words | **Intent-based** (Google 2025): Validate 1,200–2,000; Explore 2,000–3,500; Compare 600–1,200; Do 900–1,500; Know 300–800. Informational ~40% longer than transactional. **Avoid**: Under 300 words (thin); over 7,000 (often underperforms due to reduced focus). ## Content Creation Workflow ### Four Inputs Article content rests on **four inputs**. See **article-page-generator** for full workflow. | Input | Purpose | |-------|---------| | **Product** | Connection, features, CTA placement | | **Keywords** | Target keyword, primary/secondary | | **Article intent** | Informational, commercial, transactional | | **Competitor articles** | Structure to adopt, content gaps, length target | ### Information Gain (Content Density Over Word Count) **Information gain** = net new information a page provides beyond what exists in top-ranking results. Google evaluates unique value, not comprehensiveness. Content density (unique entities, data points, insights per 100 words) matters more than word count. Skyscraper Technique (longer = better) no longer differentiates; AI made comprehensiveness cheap. **Four sources of information gain**: - **Counter-narratives**: Why "best practice" fails in certain contexts; evidence-backed - **Temporal freshness**: Data or developments after competitors' content and LLM cutoff - **SME perspectives**: Direct quotes, practitioner experience; not repackaged advice - **Proprietary data**: Original surveys, internal benchmarks, user behavior patterns **Avoid consensus content**: Restating common facts across top 10 results = zero information gain. Audit SERP before writing; list the "consensus layer"; identify gaps (unanswered questions, outdated data, underserved segments). Lead with what is new; structure answer-first. **Density check**: Count unique data points, original insights, specific claims. If ratio of new information to word count is low, cut filler. High-density content (800-1,500 words with 3+ original points) often outperforms long rehashed guides. ### TL;DR or Key Takeaways (GEO) Choose one; place after intro. Content with these elements tends to be cited more frequently by AI engines. | Format | Spec | |--------|------| | **TL;DR** | 50–100 word bold summary paragraph | | **Key Takeaways** | 5–7 bullet points | See **generative-engine-optimization** for full GEO strategy. ### Introduction **Length**: 40–120 words; 2–3 paragraphs. Readers decide in ~8 seconds; hook must work instantly. | Element | Guideline | |---------|-----------| | **Hook** | First 1–2 sentences: pain point, stat, or question; curiosity gap; specific data or contrarian fact | | **Primary keyword** | In first 100 words | | **Expectations** | Set what reader will learn | **Hook types**: "You're doing X wrong"; "97% of Y…"; bold question; challenge assumption. Well-crafted hooks boost CTR 30–50%. ### Body | Element | Guideline | |---------|-----------| | **QAE pattern** | Question (H2) → Answer (2 sentences) → Evidence (data, examples, lists) | | **Answer-first** | Direct answer in first 40–60 words after each H2 | | **Answer blocks** | 100–200 words per section; direct answer + context + evidence | | **Paragraph length** | 40–80 words; 2–4 sentences; avoid walls of text | | **Break long blocks** | Lists, H3s, images, callout boxes every 2–3 paragraphs | | **Scannability** | Front-load key info (F-pattern); **bold** key phrases; one idea per paragraph | **Long-form (1,000+ words)**: Place engagement hooks every 500–600 words; mix 40–50% explanatory text, 20–25% examples, 10–15% data, 5–10% visuals. ### Conclusion **Summary** + **CTA**: newsletter signup, related content, **product** (link to product/feature when relevant). Product-linked content ties to product naturally. ### Product Connection Articles should tie to the product (problem it solves, features, use cases). Avoid purely generic content. Link to product/feature pages naturally in conclusion or when context fits. ## Writing Frameworks Apply **copywriting** frameworks to article structure. See **copywriting** for full PAS, AIDA, BAB. | Framework | Article use | |-----------|-------------| | **AIDA** | Intro (Attention); body (Interest, Desire); conclusion (Action/CTA) | | **PAS** | How-to guides: Problem in intro; Agitation in body; Solution throughout | | **BAB** | Case studies, transformation: Before → After → Bridge | **Choose by audience**: AIDA for ready-to-buy; PAS for pain-driven; BAB for transformation seekers. ## Article Headlines See **copywriting** for headline formulas (How to, Number, Problem→Solution). For article titles specifically: - **Length**: 50–60 chars; see **title-tag** - **Primary keyword** near start - **Numbers** and power words boost CTR ~36% ## References & Citations | Scenario | Practice | |----------|----------| | **Data or statistics** | Cite inline (e.g. "According to [Source](url), 72% of…") or in References section | | **Expert quotes** | Attribute; link to source | | **Reference section** | For 5+ citations; list at end before Related posts | | **Format** | Inline links preferred; numbered refs [1], [2] for academic-style | See **eeat-signals** for E-E-A-T, author bio, citations, YMYL. ## Content Quality | Element | Guideline | |---------|-----------| | **Readability** | Grade 8–10 (Flesch-Kincaid); short sentences, clear language | | **Depth** | Match type; comprehensive coverage over padding | | **Originality** | Unique angle, data, examples; avoid thin or rehashed content | | **Information gain** | What does this add that top 10 results don't? Counter-narrative, fresh data, SME quote, or proprietary insight | | **E-E-A-T** | Author bio, citations, expert quotes — see **eeat-signals** | ## Content Audit Checklist When auditing or optimizing article content: | Dimension | Check | |-----------|-------| | **Hook** | Intro opens with pain point, stat, or question? | | **Keyword in first 100 words** | Primary keyword present? | | **QAE pattern** | H2s as questions? Answer-first (40–60 words) in each section? | | **Word count** | Matches type? (300–600 news, 1,000–2,500 cluster, 2,500+ pillar) | | **Paragraph length** | 40–80 words per paragraph? No walls of text? | | **Product connection** | Ties to product? Natural links to features/pricing? | | **
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".