ehteshambuildagents bl-engage
A comment on a post with 400 reactions reaches more people than most of the user's own posts. A generic one reaches nobody and costs credibility with the author, who can tell.
Input
The user pastes the post text, ideally with the author's name and role. If they paste a screenshot, read it. If they give a URL you cannot open, ask them to paste the text. Do not scrape the feed with a browser tool, and do not guess what the post said.
Decide what the post is before deciding what to say
Read it once and classify. The classification picks the comment type; guessing produces the "Great post!" family.
| the post is | the comment that works |
|---|---|
| a claim with evidence | extend - add the case they did not cover |
| a claim without evidence | test - ask the specific question the claim invites |
| a story | echo - the parallel from your own ledger, shorter than theirs |
| a question | answer - actually answer it, first, in one line |
| a list | thirteenth item - add the one they missed |
| a mistake they admit | company - name yours, same shape, no upstaging |
| a win | mechanism - ask how, specifically. Never "congrats" alone |
| something wrong | disagree - name the disagreement, keep the person intact |
| a resource | use - say what you would do with it, not "saving this" |
Rules that matter more than the type
- Never open with praise. Start with the substance. If the praise is real, it can go at the end in four words.
- One idea. A comment that needs a paragraph break belongs in a post.
- 15 to 50 words. Longer reads as a hijack. Shorter reads as filler.
- No summary. Restating the post to prove you read it is the most common way a comment adds nothing.
- Specifics come from
ledger.md. Same rule as everywhere: no invented numbers, clients or outcomes under the user's name. - Disagree without performing. "I read this differently" then the reason. No "Respectfully, I think you'll find".
Batches
If the user wants ten comments for an engagement round, ask for all ten posts first, then write them together. Written together, they avoid repeating the same opening move ten times, which is exactly what a reader scrolling the same feed would notice.
Before you show them
Run every comment through the scrubber. Comments are where em dashes and stock phrases survive, because nobody edits a comment:
cd ../bl-scrub && python3 scrub.py comment.txt --explain
Deliver
Each comment in its own copy-ready block, labelled with the post it belongs to and the type you chose. The user posts them. This skill does not.