x-reply
Skill4 starsChanged 45 days agoMITView on GitHub
Handle the replies under the user's own X posts - sort every one, then draft answers in the order that matters. Use when the user pastes the replies on their post, says "reply to these", "handle my replies", "someone said X under my post", "how do I answer this", or is dealing with a critic, a troll or a lead in their mentions.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- belzoralolbtw/x-agent-skilltheir own version, first seen Oct 25, 2026
- swayamdhawan/x-agentword for word, first seen Oct 20, 2026
- lxyang20131208-star/x-algorithm-skillstheir own version, first seen Oct 13, 2026
Other versions3 projects use a version of this.
Word for word · 1
- swayamdhawan/x-agent★ 0100% same
Edited · 0
None found.
Wrote their own version · 2
- lxyang20131208-star/x-algorithm-skills★ 1same name
- belzoralolbtw/x-agent-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 40
Write in that order and stop when the value stops.
- Distinctive: line 53
If it is abusive, hide the reply, mute, or block, in that order of force.
≈ “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-reply
The reply section under your own post is where a post keeps going or stops.
X's published ranker weighs a predicted reply at ten times a predicted like,
and adds a boost on top when the two people follow each other (run
python3 ../x-plan/weights.py for today's values). A thread with the author
in it keeps getting served. A post the author abandoned does not.
But the value is not equal across replies, so this skill sorts before it writes.
Input
The user pastes the replies, ideally with handles. Screenshots are fine. Do not scrape the thread with a browser tool.
Triage first
Sort every reply into one bucket and say the counts out loud:
| bucket | what it is | what it gets |
| LEAD | someone describing the problem you solve | a real answer, then one sentence of open door |
| SUBSTANCE | adds data, disagrees, extends | the best reply on the thread |
| PEER | an account worth being seen next to | a reply that gives them something back |
| QUESTION | asks how, what, which | the answer, in the reply, not "DM me" |
| SUPPORT | "great post", an emoji, a tag | a like. A short reply to the first few at most |
| NOISE | spam, bots, bait, bad faith | nothing |
Write in that order and stop when the value stops.
How to reply
- Inside the first hour. That is when replying does the most for the post.
- Answer the actual question in the reply. Sending people to your DMs for an answer they could have had in public is how a thread dies.
- Match their length. A one-line reply does not get six lines back.
- To a critic: concede the true part first, in their words, then hold the line on the part you believe. Once. Never twice on the same thread.
- To a lead: answer fully in public. The open door is one sentence, an offer of help, not a pitch. Public value is what makes the next person DM.
- To bait, a bot, or a pile-on: nothing. A reply gives it reach. If it is abusive, hide the reply, mute, or block, in that order of force.
- Never quote-post a reply to dunk on it. That is a second post with their name in it, and mutes are weighted heavily against you.
Output
One block, grouped by bucket, each reply copy-ready and already through
/x-human:
REPLIES · 23 replies · 2 LEAD, 3 SUBSTANCE, 2 PEER, 4 QUESTION, 9 SUPPORT, 3 NOISE
LEAD
@sarahbuilds "we have the same problem with onboarding"
> The fix for us was deleting the welcome call and sending a 4-minute Loom
> instead. Completion went up, not down. Happy to send the script.
QUESTION
@devon_k "which model did you use for this?"
> Claude, with the skill file doing most of the work. The model mattered
> less than the file.
SUPPORT (like these; reply to the first three)
...
NOISE (3)
Skipped: two bots and a reply-guy account farming. Replying gives them reach.Then the gate: nothing is posted until the user says yes, and then the user posts each reply by hand. X's automation rules only allow automated replies to people who opted in, and this is not that.
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.