article-content
Skill23 starsChanged 2 months agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kostja94/marketing-skillsword for word, first seen Oct 21, 2026
Other versions1 project uses a version of this.
Word for word · 1
- kostja94/marketing-skills★ 1.1k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- docs/llms-full.txtllms.txt
- docs/llms.txtllms.txt
- llms-full.txtllms.txt
- llms.txtllms.txt
- seoSkill
- analytics-trackingSkill
- copywritingSkill
- podcast-marketingSkill
- translationSkill
- video-marketingSkill
- visual-contentSkill
- githubSkill
- grokipedia-recommendationsSkill
- linkedin-postsSkill
- medium-postsSkill
- pinterest-postsSkill
- reddit-postsSkill
- tiktok-captionsSkill
- twitter-x-postsSkill
- youtube-seoSkill
- entity-seoSkill
- local-seoSkill
- parasite-seoSkill
- programmatic-seoSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 101
Long-form (1,000+ words): Place engagement hooks every 500–600 words.
- Distinctive: line 154
When auditing or optimizing article content:
- Distinctive: line 173
When content is AI-assisted: human review before publish.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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, 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

