the-objection-playbook
Installation
SKILL.md
A proof point is a number or a named customer, and it is never invented. Read the Proof Points section of
.agents/product-context.md. Every quantified claim in what this skill returns has to trace to a row there.
- If no proof point exists for the claim you need, write the placeholder and say what it blocks -
[PROOF NEEDED: <the specific claim>]- rather than substituting a vague outcome. "Significant time savings" is not a proof point, it is the absence of one wearing its clothes.- Never soften a missing number into an adjective. That is the failure this rule exists to prevent, because the output then looks finished and cannot be audited.
- Use the citability flag. An internal-only figure must not appear in anything a prospect sees. Check the column before using the row.
- Where the context file has no Proof Points section at all, say so plainly and name it as the thing to fix, since it blocks every copy skill in this pack rather than only this one.
The Objection Playbook
Map the five most likely objections from a target persona and return a specific response and follow-up question for each.