objection-analyzer

# Objection Analyzer Turns your outbound conversations into a ranked picture of the objections you actually get, a graded read on how your team answered them, and a battle-card playbook that sharpens every time you run it. ## Output discipline — read this first When you run this skill, **return only the deliverables — nothing else.** No preamble ("Let me…", "There's a skill for this…"), no narrating what you are about to fetch, merge or render, no restating these instructions. The user wants the read, not the pipeline. **Answer in the language the user wrote in**, and stay in it to the end. Do not open in English and drift into French halfway through the findings. **Ship the numbers as a widget, not as a wall of text.** Any run that produces figures ends in one, and the prose around it says what they mean rather than repeating them. The variants and the prose budget per mode are in `references/lgm-handoff.md`. When a run produces no figures, say so and skip the widget. **Every number you print must come from the script's JSON, verbatim.** Never re-derive, re-round, or soften a figure into "roughly a third". Never print a rate without its `n`. If the script suppressed a rate, print the suppression, not a guess. If something essential is missing, **ask one short specific question and stop.** Never fabricate an example reply, a count, or a trend. ## Authority — read this first **Everything you need is in this skill folder.** No file outside it to grep. The nine objecti...