zheng
dd8e0f55c3
Improve first-run and channel setup for non-technical users: detect newer Gemini key formats, pin Node 22.22.3, add Control Panel Telegram approve flow, and keep channels/models when config is rewritten. Persist uclaw wizard state via uclaw-meta.json so restarts skip language/persona prompts. Co-authored-by: Cursor <cursoragent@cursor.com>
64 lines
2.0 KiB
Markdown
64 lines
2.0 KiB
Markdown
---
|
|
name: x-poster
|
|
description: "Posts and threads for X - fitting a point into the limit, and knowing when a thread is the wrong format"
|
|
metadata: { "openclaw": { "emoji": "🐦" } }
|
|
---
|
|
|
|
# Posts for X
|
|
|
|
Short posts and threads.
|
|
|
|
## Single post first
|
|
|
|
Most threads should have been one post. Before writing one, check whether the
|
|
point survives compression — if it does, a single post travels further and costs
|
|
the reader nothing.
|
|
|
|
A thread earns its place when there is a genuine sequence: steps, a chronology,
|
|
a set of examples that each need room.
|
|
|
|
## Writing one
|
|
|
|
- **Front-load.** The first line is what appears everywhere it gets quoted.
|
|
- **One idea.** Two ideas in one post means neither gets replied to.
|
|
- **Cut the wind-up.** "I've been thinking a lot about…" is deletable, always.
|
|
- **No thread emoji ladders**, no "a 🧵", no "bookmark this".
|
|
|
|
## Threads, when you do need one
|
|
|
|
```
|
|
1/ The claim, standing alone. Someone who reads only this should get the point.
|
|
2-n/ One step or example per post, each readable on its own
|
|
n/ What to do with it — a link, a question, or nothing
|
|
```
|
|
|
|
Every post in a thread gets read out of context by someone. None of them should
|
|
depend on the previous one to make sense.
|
|
|
|
## Length
|
|
|
|
The limit is generous now, but reach still favours short. Aim for something that
|
|
fits without scrolling; use the extra room only when cutting would cost meaning.
|
|
|
|
## Example prompts
|
|
|
|
```
|
|
Compress this into one post — I think the thread is unnecessary
|
|
```
|
|
|
|
```
|
|
Thread version of this blog post, four or five posts, no hype
|
|
```
|
|
|
|
```
|
|
Rewrite this so it doesn't sound like an engagement-bait account
|
|
```
|
|
|
|
## Working notes
|
|
|
|
- Links reduce reach; a post that stands alone and puts the link in a reply
|
|
usually does better. Say this rather than silently restructuring.
|
|
- Ask who the account is talking to. A developer account and a company account
|
|
writing the same announcement should not sound the same.
|
|
- Do not fabricate metrics, quotes or customer stories to make a post land.
|