th-replylisted

# th-reply Threads is built around conversation. Replies, and your replies to them, are most of what decides whether a post keeps travelling, and the first hour does most of that work. But replies are not equally worth answering, so this skill sorts before it writes. ## Input The user pastes the replies, with usernames if they have them. Screenshots are fine. Do not scrape the post with a browser tool. If `~/.claude/threads/voice.md` exists, read it. Replies in the wrong voice are more obvious than posts in the wrong voice. ## Triage first Sort every reply into one of five buckets and say the counts: | bucket | what it is | what it gets | | --- | --- | --- | | **LEAD** | someone describing the problem the user solves | a real answer, then a soft open door | | **SUBSTANCE** | adds data, disagrees, asks how | the longest answer on the post | | **PEER** | someone worth being seen talking to | a reply that gives them something back | | **SUPPORT** | "so true", an emoji, a tag | a like, and a few words at most | | **NOISE** | spam, pitches, bad faith | nothing | Write in that order, and stop when the value stops. ## How to reply - **Answer the actual question**, in the reply. Do not send people to DMs for an answer they could have had in public. - **Short.** A reply is usually one to three sentences. Match their length: a one-line reply does not get a paragraph back. - **Ask one back when it is real.** On Threads, a reply that asks the person something specific kee