Use this when writing or rewriting an X Article (long-form on x.com/i/article), with images between sections, a first-line hook, and no invented numbers.
Installs into .claude/skills of the current project.
Are you the author of X Article?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/coolxeo-x-article)
---
name: x-article
description: >-
Use this when writing or rewriting an X Article (long-form on
x.com/i/article), with images between sections, a first-line hook, and no
invented numbers.
---
# X Article
Use for X Articles (x.com/i/articles or compose/articles), not tweets or 1/2/3/4 threads.
## Form
- Title is short and concrete.
- First line of the body is the hook. If it is weak, change the entry point before polishing.
- Research body: question → what you looked at → what you could measure → what you could not.
- Images sit between sections, not as a dump at the end. Diagrams that explain the next paragraph. No decoration. Cover is type-only, no product mascot on a founder/research piece.
- Closer is one usable line. Hashtags only at the end, 0–2 (`#buildinpublic` when it is actually build-in-public).
## Research rules
- No invented token counts, dollar figures, or quotes.
- Named instruments only (disk, chat volume, subagents, ad spend, HTTP bytes, git blobs).
- Do not recap ranking cards as the article. Cards support a finding.
- Source-check every claim. Unverified numbers come out.
## Pipeline
1. Outline (hook options, mechanism, evidence gaps).
2. Draft section by section.
3. Source-check.
4. No AI slop (edit, minimum change).
5. Hand a draft to whoever holds the account. Do not post.
## Voice
First person, specific, short sentences mixed with longer ones. No unrelated product-promo CTA on a founder/research Article. No press-release tone.
