article-content

kostja94/marketing-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/kostja94/marketing-skills --skill article-content
0 commentsdiscussion
summary

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.

skill.md

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, 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
how to use article-content

How to use article-content on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add article-content
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/kostja94/marketing-skills --skill article-content

The skills CLI fetches article-content from GitHub repository kostja94/marketing-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/article-content

Reload or restart Cursor to activate article-content. Access the skill through slash commands (e.g., /article-content) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.538 reviews
  • Chaitanya Patil· Dec 28, 2024

    I recommend article-content for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Kwame Menon· Dec 28, 2024

    Useful defaults in article-content — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ama Chawla· Dec 12, 2024

    Registry listing for article-content matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Piyush G· Nov 19, 2024

    Useful defaults in article-content — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Kwame Bansal· Nov 19, 2024

    I recommend article-content for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Mia Wang· Nov 11, 2024

    article-content has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Lucas Wang· Nov 3, 2024

    Solid pick for teams standardizing on skills: article-content is focused, and the summary matches what you get after install.

  • Soo Jackson· Oct 22, 2024

    We added article-content from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Shikha Mishra· Oct 10, 2024

    article-content is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Anaya Huang· Oct 10, 2024

    article-content reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 38

1 / 4