---
name: article-content
description: 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.
  Use when: The executive requests execution of this domain.
  Skip when: The task is outside the scope of this module.
metadata:
  version: 1.1.0
---


> [!IMPORTANT]
> **GFV-Adapted Skill** — This skill runs within the GetFresh Ventures infrastructure. Follow these conventions.

### GFV Infrastructure Integration

**Credentials** — Never use `.env` files. All secrets live in macOS Keychain:
```bash
security find-generic-password -s "<service>" -a "<account>" -w
```
Check `~/Documents/Code/gfv-brain/scripts/pil_config.py` for service mappings.

**Data Sources** — Before querying external APIs, check PIL first:
- `search_pil` / `smart_search` / `vector_search` MCP tools (491K+ embeddings, 81K entities)
- Supabase tables: `entity_embeddings`, `ont_entities`, `ont_facts`
- Local SQLite: WhatsApp (59K msgs), Slack (2.5K msgs), `gfv_memory.db`

**Output** — Save results to `~/Documents/Code/gfv-brain/` or PIL via Supabase. Never send external messages (email, Slack, WhatsApp) without the Executive's explicit "send it" approval.

**Active Clients**:
- **GetFresh Ventures** — Venture studio: getfreshventures.com

---



# 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 is cited ~35% more by AI.

| 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? |
| **CTA** | Placement (conclusion, mid-article); clarity; product link |
| **References** | Data/stats cited? Reference section for 5+ citations? |
| **Gaps** | What do top-ranking articles cover that this misses? |
| **Information gain** | At least one of: counter-narrative, fresh data, SME perspective, proprietary data? Or consensus rehash? |

See **competitor-research** for competitor analysis; **article-page-generator** for page structure and metadata.

## AI-Assisted Content

When content is AI-assisted: **human review** before publish; **verify facts** and add citations; **original insights** or data; avoid generic phrasing. See **eeat-signals** for E-E-A-T and AI content guidance.

## Output Format

- **Outline** (H2s with keyword placement)
- **TL;DR or Key Takeaways** (if SEO-driven)
- **Introduction** (hook + keyword)
- **Body** sections (QAE, answer-first)
- **Conclusion** (summary + CTA)
- **CTA copy** options

## Related Skills

- **article-page-generator**: Page structure, schema, metadata, layout; content goes here
- **howto-section-generator**: Dedicated HowTo step blocks (ordered steps, HowTo JSON-LD; vs FAQ)
- **copywriting**: Frameworks (PAS, AIDA, BAB); headline formulas; short conversion copy
- **content-marketing**: Article Orientations; content types
- **eeat-signals**: E-E-A-T; author bio; citations; citations format
- **keyword-research**: Keyword basis; search intent
- **competitor-research**: Content gaps; structure to adopt; SERP audit for information gain
- **content-optimization**: H2 keywords; Multimedia (tables, lists); keyword density
- **generative-engine-optimization**: GEO strategy; AI citation



## When to Trigger
- When requested by the Executive.
- When the task aligns with the core competency of this skill.

## When to Skip
- When the data or answers already exist in the PIL memory bus.
- When the task requires physical intervention or manual approval before drafting.

## GFV Integration
**Credentials** — Never use `.env` files. All secrets live in macOS Keychain:
`security find-generic-password -s "<service>" -a "<account>" -w`
**Data Sources** — Before querying external APIs, check PIL first (`search_pil`, `gfv_memory.db`).
**Output** — Save results to `~/Documents/Code/gfv-brain/`. Never send external messages without the Executive`s explicit "send it" approval.

## Anti-Patterns
- **Summarizing instead of resolving**: Do not just summarize what needs to be done. Do the work.
- **Bypassing the Gate**: Do not execute risky actions without human-in-the-loop validation.

## References
- **GFV Standard**: GetFresh Ventures Growth by Design CEO AI Kit Architecture

<verification_gate>
# Delivery Gate

STOP AND VERIFY BEFORE DECLARING THIS TASK COMPLETE.

1. Did you verify that the execution meets all documented requirements safely?
2. Ensure you have not bypassed any "requires_human_approval" constraints.
</verification_gate>

<!-- Original Community Author: kostja94 -->

---

<gxd_footer>

> **Growth by Design™** — This skill is part of the [CEO AI Kit](https://github.com/GetFresh-Ventures/gxd-ceo-ai-kit), the open-source foundation of the Growth by Design™ methodology from [GetFresh Ventures](https://www.getfreshventures.com).
>
> 🔍 **Hitting a ceiling?** The kit gives you the foundation. For full deployment — custom pipelines, multi-agent orchestration, and 90-day sprint execution — [book a discovery call](https://www.getfreshventures.com/contact).
>
> 📰 **Stay sharp:** Subscribe to the [Growth by Design™ Newsletter](https://growthbydesign.substack.com/) for operator-written playbooks on AI-powered GTM.

</gxd_footer>