li-reply

1# li-reply
2 
3The reply thread under your own post is where reach is actually decided. Every
4reply is a second engagement event on the post, and the first hour of replies
5does most of the work. But the value is not equal across comments, so this
6skill sorts before it writes.
7 
8## Input
9 
10The user pastes the comments, ideally with names and roles. Screenshots are
11fine. Do not scrape the thread with a browser tool.
12 
13## Triage first
14 
15Sort every comment into one of five buckets and say the count out loud:
16 
17| bucket | what it is | what it gets |
18| --- | --- | --- |
19| **LEAD** | someone describing the problem you solve | a real answer + a soft open door |
20| **SUBSTANCE** | adds data, disagrees, extends | the longest reply on the thread |
21| **PEER** | a name worth being seen next to | a reply that gives them something |
22| **SUPPORT** | "great post", 🔥, a tag | a like, and a 3-8 word reply at most |
23| **NOISE** | pitch, spam, bad faith | nothing, or one line and out |
24 
25Then write in that order, and stop writing when the value stops.
26 
27## How to reply
28 
29- **Answer the actual question.** If someone asks how, tell them how, in the
30  reply. Do not send them to a DM to hear the answer they could have had.
31- **Use their name once**, at the start, and never with an exclamation mark.
32- **Match their length.** A two-line comment does not get a six-line reply.
33- **To a critic:** concede the true part first, in their words, then hold the
34…