bl-threadlisted

# bl-thread The thread under a post is where its reach is decided. Every reply is a second engagement event, and the first hour does most of the work. But the comments are not worth the same amount, so this skill sorts before it writes. ## Input The user pastes the comments, ideally with names and roles. Screenshots are fine. Do not scrape the thread with a browser tool. ## Sort first, and say the counts out loud | bucket | what it looks like | what it gets | | --- | --- | --- | | **LEAD** | describes a problem the user solves, or asks about working together | a real answer today, then a move to DM | | **SUBSTANCE** | disagrees, adds evidence, or asks a hard question | the longest reply in the thread | | **PEER** | someone worth knowing, adding their own angle | a reply that gives them something back | | **SUPPORT** | agreement, a short story, genuine warmth | two lines, by name, no boilerplate | | **NOISE** | "Great post", tagging, pitching, bots | a reaction, or nothing | Tell the user the counts before writing: "14 comments: 1 lead, 3 substance, 4 peer, 5 support, 1 noise." That alone tells them how the post did, and it is information the reaction count does not carry. ## Then write, in that order **LEAD.** Answer the actual question first, in public, properly. Do not open with "DM me" - answering in the thread is what makes the next person ask. Move to DM only after the answer, and only if there is a real reason. **SUBSTANCE.** These deserve the most effort, espe