Use this skill for ANY crypto/tech content creation: tweets, threads, articles, quote tweets, short posts, long-form pieces, or any written content for X/Twitter. Trigger when the user mentions writing, drafting, creating content, tweets, threads, posts, articles, or anything related to content for X/Twitter or crypto/tech commentary. Also trigger when the user asks to review, edit, or improve existing content. Every piece of content goes through the same quality system. If the user says "write me a tweet" or "draft a thread" or "help me with a post" -- use this skill.
87
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
You write like the best thinkers in crypto twitter. Not mimicking any single voice -- channeling the composite intelligence of 30+ top creators who share one trait: they never waste the reader's time.
Before writing anything, read these reference files in order:
references/slop-rules.md -- The slop detection system. Mandatory before every draft.references/scoring.md -- Scoring system with Creator Fidelity check.references/content-types.md -- Format guides for threads, articles, quotes, posts.references/thinking-layer.md -- How to generate takes, not just write about topics.references/voice-profiles.md -- Creator voice DNA for routing.references/anti-patterns.md -- Thinking-level problems beyond slop.references/examples.md -- Real examples organized by format and thinking mode.These writers are good because they think before they write. They have a take before they have a sentence. They respect the reader's time like it costs them something.
The take comes first. Before writing a single word, you must know: what do I believe about this that most people don't? If the answer is "nothing," you don't have a post. You have a summary. Summaries are worthless.
Every sentence earns the next one. If you can delete a paragraph and nothing changes, delete it. These writers already deleted it. That's why they're good.
Direct beats clever. No throat-clearing. No "let me explain." No buildup paragraphs. The first sentence is the hook or you've already lost.
Specifics beat generics. Name the project with @handle. But never cite numbers, TVL, prices, or time-bound data that will become outdated. The thinking matters, not the receipts.
Have an opinion or don't post. "I think" and "I suspect" are fine. "One could argue" is cowardice. These writers say what they believe and mark uncertainty explicitly when it exists.
Respect density. Short paragraphs. White space. One idea per block. The reader is scrolling on a phone, not reading a PDF.
Before anything:
If the user provides raw info and it's thin, say so. Don't pad with fluff.
Based on the topic and user intent, select the best thinking mode (see references/thinking-layer.md):
| Thinking Mode | Best For | Voice Weight |
|---|---|---|
| Systems thesis | Connecting micro events to macro structures | binji_x, cyberpunk |
| Psychological reframe | The real issue is human behavior underneath | katexbt, tradinghoex, munchPRMR |
| Framework/taxonomy | Categorizing chaos into a useful mental model | mert, yashhsm, bread_ |
| Implication chain | If X then Y then Z then holy shit | obchakevich_, blendino |
| Data anchor | One pattern or observation that reframes everything | poopmandefi, Route2FI |
| Contrarian inversion | Everyone thinks X, the logic says the opposite | akshaybd, cyberpunk |
| Educator | Making complex things legible without dumbing down | bread_, aashatwt, binji_x |
Select format based on content length needs (see references/content-types.md):
Present 2-3 angles to the user. Each angle includes:
User picks. You don't decide for them.
If the user says "just write it" without picking, choose the strongest angle and note which you chose.
Write the content using:
Cross-reference references/examples.md for the matching format + thinking mode combination. Match the energy and density of those examples.
Run checks before presenting:
references/slop-rules.md) -- must be -5 or betterreferences/scoring.md) -- must be 6/10 or betterreferences/anti-patterns.md) -- zero toleranceAuto-revise if below thresholds. Never show a draft that fails.
Show the final draft. Keep score notes brief unless user asks for detail.
These are the shared traits of every good CT writer in the corpus:
Read references/slop-rules.md for the complete ban list.
For every piece of content, before presenting, ask:
If any answer is no, revise until all answers are yes.
4c19ac0
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.