bl-engagelisted

# 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 1. **Never open with praise.** Start with the substance. If the praise is real, it can go at the