x-article-writer
Skill43 starsChanged 4 months agoMITView on GitHub
Use when writing or rewriting longform X/Twitter articles, X Articles, founder essays, launch essays, growth teardowns, product breakdowns, build-in-public stories, or sharp startup takes that need X-native hooks, tone, pacing, and structure. Use for X Articles and long posts, not blog SEO posts, lifecycle emails, or landing page copy.
In this repository25 other files it gives its agents.
- ab-testingSkill
- ai-seoSkill
- analytics-trackingSkill
- cold-outreachSkill
- competitor-analysisSkill
- content-strategySkill
- copywritingSkill
- creative-briefSkill
- cro-auditSkill
- customer-researchSkill
- distribution-planSkill
- ecommerce-app-croSkill
- email-sequenceSkill
- goalSkill
- launch-loop-strategySkill
- launch-strategySkill
- marketing-briefSkill
- marketing-planSkill
- offer-designSkill
- paid-adsSkill
- partnershipsSkill
- positioningSkill
- retentionSkill
- sales-enablementSkill
- seo-strategySkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
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 8
Write like a founder with a point of view, not a content marketer filling a page.
- Distinctive: line 33
Do not mix three spines. One article gets one main argument.
- Distinctive: line 37
Write 8-12 title or opening-line options before the body.
- Distinctive: line 51
Keep the article moving in short blocks:
- Distinctive: line 56
Specifics: use product details, examples, screenshots, numbers, customer language, channels, tools, timelines, or decisions.
- Distinctive: line 60
Every paragraph should either add tension, explain the mechanism, or give evidence.
- Distinctive: line 72
Use "I" when the piece is based on lived experience.
- Distinctive: line 73
Use named companies, products, channels, metrics, or situations when available.
- Distinctive: line 90
If a draft feels boring, AI-ish, too polished, or too much like a blog:
- Distinctive: line 92
Do not line-edit first. Rebuild the hook, opening screen, section order, and close.
- Distinctive: line 95
Remove balanced essay phrasing and consulting-deck transitions.
- Distinctive: line 101
Before final output, check:
≈ “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
X Article Writer
Write like a founder with a point of view, not a content marketer filling a page.
What Good Looks Like
A strong X article does three jobs fast:
- Stop the scroll: the title or first line creates a gap.
- Create tension: the reader sees what most people misunderstand.
- Pay it off: the body gives a mechanism, example, teardown, or playbook worth saving.
It should feel like a smart person on X making a sharp case in public, not a blog post pasted into X.
Pick The Spine
Choose one structure before drafting:
| Spine | Use When | Shape |
| I changed my mind | The piece has a lesson or reversal | I believed X -> reality showed Y -> now I do Z |
| Everyone is looking at the wrong thing | The obvious take is lazy | People blame X -> the real lever is Y -> here is why |
| Teardown | There is a product, launch, funnel, ad, or channel to analyze | What happened -> why it worked/failed -> what to copy |
| Field note | There is a call, customer, metric, launch, or experiment | Scene -> observation -> broader lesson |
| Playbook | The reader should leave with steps | Outcome -> constraints -> exact moves -> failure modes |
| Market shift | Something has changed in a category | Old rule -> new behavior -> what founders should do now |
Do not mix three spines. One article gets one main argument.
Build The Hook
Write 8-12 title or opening-line options before the body. Use one of these patterns:
- Result with friction: "We got [result]. The weird part was [unexpected cause]."
- Wrong belief: "Most founders think [X]. That's why they miss [Y]."
- Specific scene: "I was looking at [dashboard/call/page] and one thing made no sense."
- Named teardown: "[Company/product/channel] is a masterclass in [specific mechanism]."
- Useful promise: "How to get [outcome] without [common painful tradeoff]."
- Category fight: "[Category] is moving from [old rule] to [new rule]."
- Confession: "I used to think [X]. I was wrong."
Good hooks create curiosity plus stakes. Bad hooks announce the topic.
X-Native Body Shape
Keep the article moving in short blocks:
- First screen: hook, sharp claim, or scene. No throat-clearing.
- Why people get it wrong: name the common but flawed assumption.
- The mechanism: explain what is actually happening.
- Specifics: use product details, examples, screenshots, numbers, customer language, channels, tools, timelines, or decisions.
- Expansion: show why this matters beyond the example.
- Close: end with a compressed line the reader could quote.
Every paragraph should either add tension, explain the mechanism, or give evidence. If it only sounds nice, cut it.
Voice Rules
Default voice:
- Direct, specific, opinionated.
- Founder-to-founder, not analyst-to-audience.
- Short paragraphs, often 1-3 lines.
- Sentence fragments are allowed.
- Punchy transitions are allowed.
- Lower-case is fine if it matches the user's voice.
- Use "I" when the piece is based on lived experience.
- Use named companies, products, channels, metrics, or situations when available.
Avoid:
- "In today's fast-paced world"
- "The key insight is"
- "This highlights the importance of"
- "Founders need to understand"
- "It is worth noting"
- "Not only X, but Y"
- tidy essay intros
- generic LinkedIn lessons
- motivational endings
- fake guru certainty
Rewrite Mode
If a draft feels boring, AI-ish, too polished, or too much like a blog:
- Do not line-edit first. Rebuild the hook, opening screen, section order, and close.
- Make the first 5 lines do more work.
- Replace general advice with a scene, teardown, opinion, or mechanism.
- Remove balanced essay phrasing and consulting-deck transitions.
- Make the claim sharper, then make the proof or example carry it.
- End with a line that compresses the point, not a summary paragraph.
Quality Check
Before final output, check:
- Would the title make the target reader click or save?
- Is the first screen stronger than the original draft?
- Is there a clear fight, surprise, or useful promise?
- Does the body reveal new information every few lines?
- Does it sound native to X, or like a blog in short paragraphs?
- Is the ending memorable without sounding motivational?
Output
Spine:
[chosen structure]
Hook/title options:
1. [hook]
2. [hook]
3. [hook]
4. [hook]
5. [hook]
Recommended hook:
[hook + why]
X Article:
[full draft]
Why this works:
- Hook lever:
- Tone:
- Structure:
- Strongest line:
- Optional visual: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.

