Article Content
Draft long-form blog and guide body copy with clear structure, scannability, and intent-matched word counts before you wire up page SEO or publish.
Overview
Article-content is an agent skill most often used in Grow (also Launch, Validate) that drafts blog and long-form article bodies with structure, density, and intent-aware length before you handle page SEO elsewhere.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill article-contentWhat is this skill?
- Scopes intro, body sections, conclusion, and CTA—not page structure, schema, or metadata (use article-page-generator)
- QAE pattern, hooks, paragraph length, and scannability rules for readable long-form
- Word-count guidance tied to article type and search intent
- Applies AIDA, PAS, and BAB frameworks to article sections
- Explicit handoffs: article-page-generator for on-page SEO, blog-page-generator for indexes, copywriting for short conver
- Writing frameworks AIDA, PAS, and BAB applied to article sections
- Skill version 1.1.1 in SKILL metadata
Adoption & trust: 1k installs on skills.sh; 586 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know the topic and audience but stare at a blank page unsure how to structure a long post with enough depth to earn clicks and trust.
Who is it for?
Solo builders publishing SEO-minded how-tos, listicles, and guides who want body copy first and will handle metadata in a separate step.
Skip if: Short landing-page hooks, paid ad lines, or full HTML/schema pages—use copywriting or article-page-generator instead.
When should I use this skill?
User wants article body, blog post content, long-form draft, how-to or listicle text, or mentions information gain or content density.
What do I get? / Deliverables
You get a structured article draft (intro, sections, conclusion, CTA) sized for intent, ready to paste into your CMS or pair with article-page-generator for on-page SEO.
- Structured article draft with intro, body sections, conclusion, and CTA
- Intent-aligned length and scannability guidance
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Grow → Content because the skill focuses on producing article bodies that fuel compounding traffic and authority, not on page schema or ad copy. Content subphase matches blog posts, how-tos, and listicles—the repeatable editorial work solo builders use to teach and rank.
Where it fits
Turn a product lesson into a scannable how-to with hooks and a closing CTA for your newsletter site.
Draft the substantive sections first so metadata and internal links in article-page-generator have real copy to wrap.
Write a deep explainer article body that supports a waitlist page without conflating it with short landing hero copy.
How it compares
Use for article body prose; use article-page-generator when you need page structure and SEO metadata, not copywriting for one-liner CTAs.
Common Questions / FAQ
Who is article-content for?
Indie founders, marketers, and agent users who publish blogs and guides and want structured long-form drafts without mixing in schema or ad-style copy.
When should I use article-content?
During Grow content sprints, Launch SEO planning when you need the narrative before metadata, or Validate when a long explainers supports your offer—whenever you say write article, listicle, or how-to body.
Is article-content safe to install?
It is editorial guidance only; review the Security Audits panel on this Prism page before installing any skill from the catalog.
Workflow Chain
Then invoke: article page generator, blog page generator
SKILL.md
READMESKILL.md - Article Content
# 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 "consen