Agent skill · Content & Marketing

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.

kostja94github.com/kostja94GitHub ↗
cursorMIT
Install
npx skills add kostja94/marketing-skills --skill article --agent cursor

Same command for any agent — swap --agent for claude-code, codex, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 10 KB
Bundled scripts: none
Version: 1.1.1
Path: skills/content/article/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 848

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the 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 update

What's inside
Steps it walks through
  1. Scope
  2. Article Types & Word Count (2025)
  3. Content Creation Workflow
  4. Four Inputs
  5. Information Gain (Content Density Over Word Count)
  6. TL;DR or Key Takeaways (GEO)
  7. Introduction
  8. Body
  9. Conclusion
  10. Product Connection
  11. Writing Frameworks
  12. Article Headlines
  13. References & Citations
  14. Content Quality
More from marketing-skills
All skills →
About this skill
What does the article-content skill do?

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.

How do I install it?

Run `npx skills add kostja94/marketing-skills --skill article --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From kostja94/marketing-skills, a repository with 848 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going