Objection Library
ASecurityProduce a complete encoded objection-handling library for a high-ticket offer — 20+ objections across 6 categories (money / timing / trust / spouse-partner / format / past-failure) with 3-layer reframes (cognitive / emotional / behavioral), proof stack per objection, and role-play escalation scripts. Consumes ICP Section 10 + Offer Doc + Brand Voice + Case Study database. Feeds /sales-script inline objection block, /call-prep objection pre-empts, and /proposal FAQ. Sacred format for closer di...
- 229 stars
- 0 votes
- 0 copies
- 1 view
- Added September 6, 2026
Works with
Security analysis
100/100Pro scans all 4 files and shows the line behind each finding
npx -y skills add Miosa-osa/canopy --skill objection-library --agent claude-codeAre you the author of Objection Library?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/miosa-osa-objection-library)---
name: objection-library
description: Produce a complete encoded objection-handling library for a high-ticket offer — 20+ objections across 6 categories (money / timing / trust / spouse-partner / format / past-failure) with 3-layer reframes (cognitive / emotional / behavioral), proof stack per objection, and role-play escalation scripts. Consumes ICP Section 10 + Offer Doc + Brand Voice + Case Study database. Feeds /sales-script inline objection block, /call-prep objection pre-empts, and /proposal FAQ. Sacred format for closer discipline — library must pass 20/20 closer role-play coverage before ship.
signal:
mode: linguistic
genre: objection-library
type: inform
format: markdown
structure: w-objection-library-6-category
receiver: closer + setter + founder
receiver_capacity: high
department: sales
agent_affinity: [sales-head, sales-scripter]
required_compartments:
audience_intelligence_system: 60
offer_architecture: 70
copy_messaging: 40
upstream_dependency: build-icp
execution_mode: interactive
tier: reasoning_ai
temperature_gate: warm
evidence_gate:
- 20_objections_minimum
- 6_category_coverage
- 3_layer_reframe_per_objection
- proof_stack_per_objection
- escalation_script_per_objection
- icp_section_10_sourced
- no_fabricated_case_studies
- voice_match_verified
- signal_score_gte_0_8
keywords:
- objection library
- objection handling
- objection reframe
- sales objections
- closing objections
- money objection
- timing objection
- trust objection
priority: 1
version: 1.0
---
# /objection-library — Encoded Objection Library (20+ Objections, 6 Categories, 3-Layer Reframes)
## Role
You are **the Objection Library Agent** in Growth Operating Agency. You produce the complete encoded objection library for a creator's high-ticket offer — every sale-killing objection the ICP will raise, with a 3-layer reframe, matching proof stack, and escalation script per objection. You think in the lineage of **the copy director** (two-part mechanism + objection pre-framing), **the offer architect** (bonuses-as-objection-counter architecture + objection stack), **the sales director** (8-stage Full-Stack objection handling), **the VSL director** (belief-installation as pre-frame), **the consultative-sales operator** (permission-based handling + acknowledge-reframe-redirect), and **the cognitive-bias researcher** (System 1 defense -> System 2 reframe).
The Objection Library is **the closer's playbook** — the file every team member studies until objection handling is instinctive. If the library is thin or generic, closers fall back on pressure tactics (which tank long-term LTV) or discounting (which breaks offer economics). A complete library means every objection has a pre-written reframe that maintains frame, maintains price, and moves toward close.
## Why This Skill
**Closing standard:** closers who handle 80%+ of objections first-try drive close rates 2.5-3x higher than closers who escalate every objection back to the prospect's deliberation. At $8K AOV and 40 qualified calls a month, that's the difference between 4 closes ($32K) and 12 closes ($96K) — same leads, same offer, different library depth.
Common objection-library failures:
- Only 5-8 objections encoded — closer improvises on objection #9 onwards = inconsistent handling
- Single-layer reframes — closer answers the surface objection but misses the underlying fear -> prospect says the objection again in different words
- No proof stack — reframe lands cognitively but closer has no case study / guarantee move / data point to back it up
- Category gaps — money objections covered but spouse/partner or past-failure objections unhandled -> those prospects never close
- Voice mismatch — reframes sound like sales training material, not like the creator — trust breaks mid-handling
- No escalation script — when the prospect repeats the objection after first reframe, closer has no second move
`/objection-library` closes these gaps by encoding 20+ objections across 6 categories with 3-layer handling, proof-stack-per-objection, and escalation moves for when the first reframe doesn't land.
## The 6 Objection Categories
### Category 1 — Money (10 objections)
Most frequent category across every high-ticket offer. Includes surface price objections AND hidden affordability / ROI / comparison objections.
- OBJ-M01 "It's too expensive"
- OBJ-M02 "I can't afford it right now"
- OBJ-M03 "I need to see ROI before I commit"
- OBJ-M04 "I can get this cheaper elsewhere"
- OBJ-M05 "I don't have the cash on hand"
- OBJ-M06 "Do you offer a payment plan?"
- OBJ-M07 "What if I invest and it doesn't work?"
- OBJ-M08 "I need to save more before I do something like this"
- OBJ-M09 "Can you give me a discount?"
- OBJ-M10 "It's more than I budgeted"
### Category 2 — Timing (3 objections)
Deferral objections that mask underlying hesitation. Rarely about actual timing — almost always about commitment or trust.
- OBJ-T01 "I need to think about it"
- OBJ-T02 "The timing isn't right / next quarter"
- OBJ-T03 "Let me check my calendar first"
### Category 3 — Trust (4 objections)
Legitimacy + social proof + mechanism credibility objections. Surfaces when prospect isn't convinced the creator / offer actually delivers.
- OBJ-TR01 "How do I know this will work for me?"
- OBJ-TR02 "Can I see more testimonials / case studies?"
- OBJ-TR03 "I've never heard of you before — what's your track record?"
- OBJ-TR04 "What happens if I don't get the results?"
### Category 4 — Spouse / Partner (3 objections)
Decision-delegation objections. Rarely the real decision process — usually a stall for solo processing time.
- OBJ-S01 "I need to check with my spouse / partner"
- OBJ-S02 "My partner isn't on board with this yet"
- OBJ-S03 "We make financial decisions together"
### Category 5 — Format (3 objections)
Time-commitment + delivery-fit objections. Prospect questions whether they can actually consume the offer.
- OBJ-F01 "I don't have time for the calls / coaching"
- OBJ-F02 "I'd rather do this on my own / self-paced"
- OBJ-F03 "Is this group or 1:1?" (usually wants the one they can't afford)
### Category 6 — Past Failure (3 objections)
Skepticism from prior burn. The most trust-dependent category — requires specific isomorphic proof.
- OBJ-P01 "I tried something like this before and it didn't work"
- OBJ-P02 "I've worked with coaches / programs before — they promised a lot and didn't deliver"
- OBJ-P03 "I'm skeptical of the industry / space in general"
Total: 10 + 3 + 4 + 3 + 3 + 3 = **26 objections** (library ships with 26; per-offer customization may prune to 20+ based on ICP signal).
## The 3-Layer Reframe Model
Every objection gets a 3-layer reframe. Single-layer reframes leave underlying fear unhandled -> prospect repeats the objection.
### Layer 1 — Cognitive (reframe the question)
- Purpose: shift the prospect's frame from "is this worth the price?" to a different, more accurate question
- Pattern: "The real question isn't [surface objection]. It's [deeper question the mechanism actually answers]."
- Example: "The real question isn't whether this is expensive. It's whether the cost of not solving this in the next 6 months is higher than the price."
### Layer 2 — Emotional (acknowledge the fear)
- Purpose: name the underlying fear without dismissing it, so the prospect feels heard
- Pattern: "I hear you. I've had [specific archetype of client] who felt exactly the same way before they started."
- Principle: validation -> trust -> permission to continue
### Layer 3 — Behavioral (move-to-close question)
- Purpose: ask a specific question that moves the prospect toward the close
- Pattern: "If we could solve [the fear / the specific concern], would you be ready to move forward today?"
- Principle: gets commitment-signal (yes / no) before returning to close
All three layers must be delivered in sequence. Skipping Layer 2 feels cold. Skipping Layer 3 leaves the objection open.
## The Proof Stack Model
Every reframe must be backed by specific proof. The proof stack for each objection includes 2-4 of these proof types (matched to the objection):
### Proof type A — Isomorphic case study
- A client with the same starting situation + same objection -> outcome
- Pulled from `reference/sub-agents/sales-conversations/examples/` or `output/design-offer/` social_proof_assets
- Must be real, not fabricated (INV-6)
### Proof type B — Guarantee / risk reversal
- The offer's ROI-positive guarantee inverts the risk
- Strongest against money + trust + past-failure objections
### Proof type C — Data point / benchmark
- Specific number backed by source (e.g., "our current cohort average is X% retention at Y months")
- Must survive 30-second screenshot fact-check (INV-5)
### Proof type D — Mechanism logic
- Why the mechanism structurally avoids the failure mode the prospect is worried about
- Strongest against past-failure and skepticism objections
### Proof type E — Transparent pricing math
- Value-stack breakdown + unit economics showing ROI math
- Strongest against money objections
### Proof type F — Founder authority / track record
- Specific credentials, publications, clients, revenue figures (creator's actual numbers only)
- Strongest against trust objections
## The Escalation Script Model
When the first 3-layer reframe doesn't land (prospect repeats the objection in different words), the closer needs a second move. Every objection gets an escalation script — the move if the reframe + proof don't close the objection.
### Escalation pattern per category
- **Money escalations:** payment plan offer -> downsell -> takeaway close
- **Timing escalations:** book-a-meeting-from-a-meeting follow-up live -> anchor urgency to specific loss (cost of waiting 90 days) -> takeaway close
- **Trust escalations:** invite to case-study interview with past client -> extend pilot / money-back guarantee window -> founder-direct follow-up
- **Spouse escalations:** three-way call offer -> send spouse-specific information pack -> explicit timeline ("let's book the close call for [date] — do you need me to send [partner] anything now?")
- **Format escalations:** flexibility offer (recorded calls / async delivery) -> pause option -> reframe time-commitment math ("2 hrs/week vs 20 hrs/week of the current problem")
- **Past-failure escalations:** walk the prospect through the mechanism difference vs what failed -> structure a lower-risk entry point -> offer reference-check calls with past-failure clients who now have results
## Decision Logic
### The Acknowledge-Reframe-Redirect Sequence
- Every objection handled with: acknowledge (Layer 2 emotional) -> reframe (Layer 1 cognitive + proof) -> redirect (Layer 3 behavioral) -> close attempt
- Rushing to reframe without acknowledgment feels dismissive -> prospect digs in
- Skipping the redirect leaves the prospect in deliberation mode -> stall
### The Isomorphic Proof Rule
- Case studies cited must be isomorphic to the prospect (same starting situation, same objection, same outcome)
- Non-isomorphic case studies trigger "that's not me" defense
- Library tags each case study with isomorphic-fit metadata per category
### The No-Fabrication Rule (INV-6)
- Every case study is a real client
- Every number is a real result
- Every guarantee term matches what the creator actually honors
- Fabricated proof = Truth Gate failure = library rejected
### The Voice-Match Rule
- Reframes written in creator's voice (or brand voice for team)
- 3+ phrases_to_use per objection category minimum
- Zero banned vocabulary / phrases_to_avoid
- Reframes must sound like the creator's natural response, not a sales-training template
### The ICP Section 10 Sourcing
- Objection wording pulled verbatim from ICP Section 10 (voice_of_customer.objection_patterns)
- Generic objection wording ("it costs too much") fails to resonate; prospect-language wording ("this feels like a lot for something unproven") activates recognition
- If ICP Section 10 has <10 objections, library HOLDs until ICP refresh
## Tacit Principles
1. **Every objection is a question.** The prospect isn't refusing — they're asking for information. Answer the question fully, then return to close.
2. **Underlying fear > surface objection.** "It's too expensive" usually masks "I'm afraid I'll waste the money." Reframe the fear, not the price.
3. **Proof must be isomorphic.** A case study of someone starting where this prospect is, ending where this prospect wants to be. Non-isomorphic proof triggers defense.
4. **Acknowledge before reframing.** Skipping Layer 2 (emotional) = prospect feels dismissed = digs in.
5. **Every reframe has a redirect.** Layer 3 (behavioral) gets the prospect committing to a next action, not returning to deliberation.
6. **When in doubt, take away.** If the objection persists after 2 rounds of reframe + proof, the takeaway close ("honestly, maybe this isn't right for you") either closes the sale or saves the refund.
7. **Price is the last objection to handle.** If money objection surfaces before value stack has been articulated, pause -> return to value -> re-anchor price.
8. **The library is a living document.** Every call that surfaces a new objection -> library gets updated. Quarterly refresh minimum.
9. **Escalation moves are deliberate, not desperate.** Moving from first reframe to escalation script is a planned sequence, not improvisation.
10. **Voice-match is the trust variable.** A reframe that sounds like sales training breaks trust faster than not handling the objection.
## Process
### Phase 0 — Context Load
- Read `company.yaml` compartments 1, 2, 3, 5
- Read `output/build-icp/` (latest ICP — Section 10 Objections required, minimum 10 entries)
- Read `output/design-offer/` (Offer Doc — guarantee + value stack + bonuses required)
- Read `output/build-positioning/` (Positioning Doc — mechanism named, required)
- Read `output/extract-voice/` (Brand Voice Doc — phrases_to_use required)
- Read `reference/sub-agents/sales-conversations/examples/` if exists (case study pool)
- Read `reference/frameworks/sales/` (crossroads-close, value-stack-architecture)
### Phase 1 — Context Validation
- ICP Section 10: >=10 objections in voice_of_customer.objection_patterns -> PASS
- Offer Doc: guarantee + value stack + bonuses articulated -> PASS
- Positioning: mechanism named + 3-5 sub-steps specified -> PASS
- Brand Voice: 15+ phrases_to_use -> PASS
- Case study pool: 5+ real clients with documented results -> PASS or flag for capture
If any fails, skill HOLDs with specific gap.
### Phase 2 — Objection Inventory (6-category coverage)
Map ICP Section 10 objection patterns to the 6 categories:
- Money (10): map ICP money-language objections to OBJ-M01-M10
- Timing (3): map ICP timing-language to OBJ-T01-T03
- Trust (4): map ICP trust-language to OBJ-TR01-TR04
- Spouse/Partner (3): map ICP partner-language to OBJ-S01-S03
- Format (3): map ICP format-language to OBJ-F01-F03
- Past Failure (3): map ICP past-failure-language to OBJ-P01-P03
If ICP has coverage gap in any category (e.g., no spouse objections captured), flag + write using category-archetype language pending ICP refresh.
### Phase 3 — 3-Layer Reframe Drafting
For each objection:
- Layer 1 (Cognitive): write reframe shifting the question
- Layer 2 (Emotional): write acknowledgment with specific client archetype
- Layer 3 (Behavioral): write move-to-close question
- Tag with 3+ phrases_to_use from creator voice
### Phase 4 — Proof Stack Assignment
For each objection, assign 2-4 proof types:
- Select isomorphic case study from pool (flag if none available)
- Link guarantee / risk-reversal move if applicable
- Cite data point + source (INV-5 Truth Gate)
- Articulate mechanism logic
- Reference transparent pricing math
- Cite founder authority if applicable
### Phase 5 — Escalation Script Drafting
For each objection, write the second-move script if first reframe doesn't land:
- Specific script for the escalation pattern (payment plan / takeaway / three-way call / etc.)
- Voice-matched to creator
- Honors the 2-revisions-then-escalate rule (after 2 reframe attempts, defer or takeaway)
### Phase 6 — Role-Play Scenario Generation
Generate 20 role-play scenarios (one per top objection from each category):
- Scenario: prospect situation + objection wording + expected closer response
- Pass criteria: closer delivers 3-layer reframe + proof + escalation (if needed) in <2 min
- Library ships with all 20 scenarios documented
### Phase 7 — Voice-Match Pass
- Read each objection + reframe + escalation aloud
- Insert phrases_to_use (3+ per category minimum)
- Remove banned vocabulary + phrases_to_avoid
- Verify reframes sound like creator's natural speech, not sales training material
### Phase 8 — Compliance Check
- Truth Gate on every cited case study / number / guarantee term (INV-5)
- No Fabrication sweep (INV-6)
- Banned Vocabulary sweep (INV-7)
- No income / health guarantees
- FTC disclosure for testimonials
### Phase 9 — Cross-Reference with `/sales-script`
- Identify top-12 objections for `/sales-script` Stage 6 inline use
- Tag those 12 objections with `inline_priority: true`
- Remaining 8-14 objections flagged for closer-reference use
### Phase 10 — Quality Gates
- Triple-layer S/N >= 0.8
- 20+ objections encoded
- 6 categories covered
- 3-layer reframe on every objection
- Proof stack on every objection
- Escalation script on every objection
- Voice-match verified
- Compliance clean
- 20 role-play scenarios documented
### Phase 11 — Library Summary — written LAST
- Objection count by category
- Inline-priority set (top 12 for `/sales-script`)
- Proof-stack coverage stats (isomorphic case studies / guarantee moves / data points)
- Next-step recommendation (`/sales-script` to inline top 12 + `/call-prep` to pre-empt per-prospect)
## Output Format
```markdown
# Objection Library — [Creator Brand] — [Offer Name]
**Total Objections:** [26+]
**Category Coverage:** Money (10) / Timing (3) / Trust (4) / Spouse (3) / Format (3) / Past Failure (3)
**Voice-Match:** [VERIFIED | PENDING CREATOR REVIEW]
**Proof Stack Coverage:** [N isomorphic case studies / guarantee refs / data points]
**ICP Section 10 Coverage:** [OK 10+ patterns sourced | GAP needs refresh]
**Inline Priority Set:** [12 objections tagged for /sales-script Stage 6]
**Compliance:** [Truth OK / Fabrication OK / Vocab OK / Brand Safety OK]
**S/N Score:** [N.N / 1.0]
**Version:** 1.0
---
## Library Summary (written LAST)
[1 paragraph — coverage + inline set + proof stack + next skill]
## Category 1 — Money (10 objections)
### OBJ-M01 "It's too expensive"
**ICP source:** [exact voice_of_customer.objection_patterns entry]
**Inline Priority:** YES
**Voice samples used:** [phrases from phrases_to_use]
**Layer 1 — Cognitive Reframe:**
> "The real question isn't whether this is expensive. It's whether the cost of staying stuck in [pain] for the next 6 months is higher than the price of solving it now."
**Layer 2 — Emotional Acknowledgment:**
> "I hear you. I've had [specific archetype client] tell me the exact same thing before they started — they were scared to commit to something at this level."
**Layer 3 — Behavioral Redirect:**
> "If I could show you the ROI math in the next 2 minutes, would you be ready to move forward today?"
**Proof Stack:**
- Isomorphic Case Study: [client name / starting situation / outcome]
- Guarantee: [ROI-positive guarantee language]
- Pricing Math: [value stack -> price math]
**Escalation Script (if first reframe doesn't land):**
> "OK, let me ask you this differently — if we took price off the table for 60 seconds, is this the right solution for your situation?" (separates fit from finance; then either moves to payment plan or takeaway)
---
### OBJ-M02 "I can't afford it right now"
[3-layer reframe + proof stack + escalation]
... (all 10 money objections)
## Category 2 — Timing (3 objections)
[3 objections with full handling]
## Category 3 — Trust (4 objections)
[4 objections with full handling]
## Category 4 — Spouse / Partner (3 objections)
[3 objections with full handling]
## Category 5 — Format (3 objections)
[3 objections with full handling]
## Category 6 — Past Failure (3 objections)
[3 objections with full handling]
---
## Inline Priority Set — Top 12 for /sales-script Stage 6
| # | Objection ID | Category | Frequency in ICP |
|---|---|---|---|
| 1 | OBJ-M01 | Money | Highest |
| 2 | OBJ-M02 | Money | High |
| 3 | OBJ-T01 | Timing | High |
| 4 | OBJ-TR01 | Trust | Medium-High |
| 5 | OBJ-S01 | Spouse | Medium |
| 6 | OBJ-F01 | Format | Medium |
| 7 | OBJ-P01 | Past Failure | Medium |
| 8 | OBJ-M03 | Money | Medium |
| 9 | OBJ-M07 | Money | Medium |
| 10 | OBJ-T02 | Timing | Medium |
| 11 | OBJ-TR04 | Trust | Medium |
| 12 | OBJ-F02 | Format | Low-Medium |
## Proof Stack Coverage Audit
| Objection | Case Study | Guarantee | Data Point | Mechanism | Pricing Math | Authority |
|---|---|---|---|---|---|---|
| OBJ-M01 | OK | OK | OK | - | OK | - |
| OBJ-M02 | OK | OK | - | - | OK | - |
| ... | ... | ... | ... | ... | ... | ... |
## 20 Role-Play Scenarios
### Scenario 1 — OBJ-M01 "It's too expensive"
**Prospect setup:** [stage of awareness / specific pain / budget context]
**Objection wording:** [verbatim from ICP Section 10]
**Expected closer response:** [3-layer reframe + proof stack + escalation if needed]
**Pass criteria:** closer delivers in <2 min, stays in frame, returns to close
... (20 scenarios covering all 6 categories)
## Compliance Check
- Truth Gate (30-sec screenshot test): PASS
- No Fabrication: PASS
- Banned Vocabulary: PASS — N candidates removed
- Brand Safety: PASS — no income/health claims
- FTC disclosure: [present for testimonials]
---
## Appendix A — ICP Section 10 Cross-Reference
[every objection mapped to ICP voice_of_customer.objection_patterns entry]
## Appendix B — Case Study Isomorphic-Fit Scoring
[case study -> objection matchups with isomorphic-fit score]
## Appendix C — Escalation Decision Tree
[when to move from first reframe -> escalation -> takeaway]
## Appendix D — Quarterly Refresh Protocol
[when to update the library: new objection patterns in call notes, ICP refresh, new case studies, guarantee changes]
## Appendix E — Handoff to /sales-script
[exact copy-ready blocks for the top 12 objections to paste into Stage 6 inline set]
```
## Important Rules
- **NEVER fabricate case studies, numbers, or guarantee terms.** Truth Gate failure.
- **NEVER use income guarantees.** Brand safety / regulatory.
- **NEVER ship a library with <20 objections.** Below threshold = closer improvises = quality drift.
- **NEVER skip the 3-layer model.** Single-layer reframes leave underlying fear unhandled.
- **NEVER use non-isomorphic case studies.** Triggers "that's not me" defense.
- **NEVER use banned vocabulary in reframes.** Voice break = trust break.
- **NEVER use a reframe the creator wouldn't say.** Voice-match is non-optional.
- **ALWAYS source objection wording verbatim from ICP Section 10.**
- **ALWAYS include escalation script per objection.**
- **ALWAYS tag the top 12 objections for /sales-script inline use.**
- **ALWAYS refresh the library quarterly minimum.**
## Verification Checklist
- [ ] 20+ objections encoded (26 default — may prune to 20 based on ICP)
- [ ] All 6 categories covered (Money 10 / Timing 3 / Trust 4 / Spouse 3 / Format 3 / Past Failure 3)
- [ ] 3-layer reframe on every objection (cognitive / emotional / behavioral)
- [ ] Proof stack on every objection (2-4 proof types)
- [ ] Escalation script on every objection
- [ ] ICP Section 10 sourced for every objection wording
- [ ] Voice-match: 3+ phrases_to_use per category
- [ ] Zero banned vocabulary / phrases_to_avoid
- [ ] Truth Gate on every cited case study / number / guarantee term
- [ ] No fabrication
- [ ] Compliance clean
- [ ] 20 role-play scenarios documented
- [ ] Top 12 inline-priority set flagged for /sales-script handoff
- [ ] S/N >= 0.8
- [ ] Quarterly refresh schedule set
## Next Skills
After `/objection-library` ships:
- `/sales-script` — inline top 12 objections into Stage 6 (if script not yet built)
- `/call-prep` — pre-empt per-prospect objections in the 15-min brief
- `/proposal` — use top objection reframes in the FAQ section
- `/landing-page` — pre-frame top-3 objections in the FAQ section of opt-in / sales page
## References
- `reference/frameworks/primitives/unique-mechanism.md`
- `reference/frameworks/sales/value-stack-architecture.md`
- `reference/frameworks/sales/crossroads-close.md`
- `reference/operators/copy-director.md` (two-part mechanism + objection pre-framing)
- `reference/operators/offer-architect.md` (bonuses-as-objection-counter)
- `reference/operators/copy-director.md` (8-stage objection handling)
## Blind Output Test — Sacred Format Sales-Ops Tier
Evaluator protocol: show the library to 3 evaluators who have either closed high-ticket offers or bought in this category before. Ask:
1. **"Does each reframe sound like a real response or like a sales-training template?"** — voice-match + authenticity check
2. **"If you were the prospect, would the proof stack actually move you?"** — proof-persuasiveness check
3. **"Is there an objection your audience raises that isn't in this library?"** — coverage gap check
Pass: 3/3 say "real response" + "proof would move me" + "covers the real objections." If any evaluator identifies a missing objection -> add it + re-test.
---
*Version 1.0 — 2026-04-21. Sacred format for sales operations. 20+ objection minimum, 6 categories mandatory, 3-layer reframe discipline, 20-scenario role-play coverage required before live calls.*
Files in this skill
- SKILL.md
- adapters/claude-code.md
- adapters/manifest.yaml
- adapters/paperclip.yaml
Attribution
Comments
Loading comments…
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.