Turn a plain sentence into a tweet readers cannot resist replying to. Just stack two things together:One real fact(credible, substantive) + One hook(leave a gap for people to fill).
Iron rules of style: short, plain, everyday ⚠️ Most important
This is where things go wrong most easily, so it has the highest priority:
- The shorter the better. A tweet is best read in one or two sentences; cut every word you can. Long = a turnoff.
- Talk like a human. Everyday colloquial speech, like talking to a friend on WeChat. No formal or literary tone, no piling on adjectives.
- No sentimentality, no moralizing, no parallelism. Don't use literary hipster phrases like "heartfelt," "as if a lifetime had passed," or "that heartbeat in that moment." Say plain everyday things plainly.
- Give the hook directly. If you want to ask, just ask; don't beat around the bush.
Contrast between right and wrong (the same nostalgic Hongqiao post):
- ❌ Too literary: "What changed is the airport; what didn't change is that heartbeat when you walk out of the terminal."
- ✅ Short and plain: "Back then this was still Shanghai's only airport; Pudong only opened in 1999. Where did you fly for the first time?"
Workflow
Step 1: Capture the core
What is the original text actually trying to say? Find the point that can be pinned down by onereal fact(an opinion, a feeling, a person/event/place).
Step 2: Search online for one real fact ⚠️ Required
The credibility of the whole tweet depends on this fact being true.
- Use
web_searchto look up aspecific enough to verifyfact: exact year/number/name/place, "first/last/only," records, counterintuitive truths. - Prefer counterintuitive ones or ones people "sort of know"—they most easily trigger "I know!" or "Really?"
- Never fabricate, exaggerate, or attribute wrongly. If you can't find it, change the angle, or say plainly "no reliable fact found." Better to change the angle than use a fake fact as a hook—that's spreading rumors and ruining the account.
- Double-check numbers, years, and names before writing them down.
Step 3: Apply different hooks and write 2-3 versions
Using the same real fact, write 2-3 versions with different hooks(what changes is the participation method, not the tone). Every version must follow the iron rules of style above. Hook types:
- Historical pattern extrapolation hook (strongest): Use 2 or more real facts to lay out a hidden pattern, extrapolate it to the present, and leave the conclusion blank for people to guess. Example: "Storage got cheap, Gmail appeared; bandwidth got cheap, YouTube appeared. Intelligence gets cheap, what will appear?"
- Question hook: Throw out a question everyone has an answer to and can reply to at zero cost. Example: "Where did you fly for the first time?"
- Fill-in-the-blank hook:Blank out a word/number that's "on the tip of your tongue" for people to fill in (the blank must be genuinely correct). E.g.: "When Beethoven wrote the Ninth, he was already completely ___."
- Counterintuitive hook:Lead with a counterintuitive truth that makes people want to argue or verify. E.g.: "You'd think X, but actually it's Y."
- Either/or / take-a-side hook:Give two options and let people pick a side—a lower bar than an open-ended answer. E.g.: "A or B? Sound off."
Don't use the same hook every time; don't sacrifice the original meaning (you're adding credibility and a hook to the original words, not changing the subject).
Output format
【版本 1 · 提问钩】
<推文正文>
↳ 钩子:一句话说明为什么勾人
【版本 2 · 填空钩】
<推文正文>
↳ 钩子:……
Append a line at the endFact sources, so users can verify.
Step 4: Image prompt (mention it if there is one, skip if not)
Posts with images spread better, and historical-fact tweets often happen to have classic photos/comparison images. After producing it, judge whether there's a ready-made, visually striking image (old photo, before/after comparison, data chart); if so, use image_search to find it and give it to the user, and remind them to prioritize public-domain sources (Library of Congress, National Archives, Wikimedia) with attribution. If there's nothing suitable, don't force it.
Benchmark examples
A real viral post, and also the style model for this skill (short, plain, factual, with a gap):
Storage got cheap, and Gmail appeared; bandwidth got cheap, and YouTube appeared. When intelligence gets cheap, what will appear?
Why it went viral: two real facts (Gmail in 2004 with 1GB, about 100 times its competitors; YouTube in 2005) lay out the pattern of "costs plummeting → era-defining products being born," then leave the conclusion blank—readers can't help responding, and can show off their foresight by making a prediction. Not a single多余的 adjective throughout.
Rewrite example
Original (opinion type): AI is getting cheaper and cheaper; in the future, some really impressive new products are sure to emerge.
【版本 1 · 历史规律外推钩】
存储便宜,出了 Gmail;带宽便宜,出了 YouTube。
智能便宜,会出什么?
↳ 钩子:真事实摆规律 + 结论留空,接话门槛极低。
【版本 2 · 反常识钩】
Gmail、YouTube 不是靠想法赢的,是踩中了成本暴跌。
这轮暴跌的是"智能",下一个 Gmail 你押谁?
↳ 钩子:打破"靠创意取胜"的直觉 + 站队式开放问题。
Fact sources: Gmail launched on 2004/4/1 with 1GB of free storage (about 100 times its competitors); YouTube was founded in 2005 and launched that December. (Verify with web_search before posting.)
Original (everyday type): Suddenly it feels like I just came out of Hongqiao Airport, just like the first time I flew to Hongqiao 30 years ago.
【版本 1 · 提问钩】
30 年前第一次坐飞机就是来的虹桥,今天又从这儿出来。
那会儿它还是上海唯一的机场,浦东 1999 年才开。
你第一次坐飞机去的哪儿?
↳ 钩子:用真事实坐实"30 年",结尾"第一次坐飞机"人人有答案,零门槛。
【版本 2 · 反差钩】
30 年前坐飞机还是全家送站的大事。
现在全国一年坐飞机超 7 亿人次,可还有近 10 亿人一次没坐过。
你坐过没?
↳ 钩子:反差数字 + "坐过没"二选一,一秒就能答。
Fact sources: Pudong Airport opened in September 1999, and Hongqiao shifted to being mainly domestic; national civil aviation passenger volume exceeded 700 million in 2024 (Civil Aviation Administration); "nearly 1 billion people have never flown" was a widely circulated estimate around 2019.
Note these two examples:The sentences are short, all plain language, with not a single sentimental line. That is the default style.
Notes
- Truthfulness > attractiveness. A factual error is far worse than being not attractive enough. If unsure, check; if you can't find it, don't use it.
- Short > complete. Better to say one less layer of meaning than to write it long and full.
- The hook must truly be low-barrier. It should be "glance at it and you can fire off a line," not "think for ages before you can answer."
- If the original already contains specific facts, prioritize verifying and reusing them; don't start from scratch.