objection-library

Extracts and ranks buyer objections from sales call transcripts by frequency and funnel stage.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/nugiwabot/marketing-branding-selling-ads-skills --skill objection-library-nugiwabot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: objection-library
Source: https://github.com/nugiwabot/marketing-branding-selling-ads-skills/tree/main/.agents/skills/objection-library
Command: npx skills add https://github.com/nugiwabot/marketing-branding-selling-ads-skills --skill objection-library-nugiwabot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sales teams typically build objection handling from the few objections reps remember most recently, missing the broader set of concerns buyers actually raise across dozens of calls. This Skill reads the full set of sales conversations and produces a ranked, evidence-backed library of real objections in the buyer's own words. ## Core Features & Use Cases - Objection Extraction & Ranking: Pulls every buyer concern, hesitation, or blocker from call transcripts, normalizes duplicate phrasings, and counts frequency across the supplied call set. - Funnel-Stage Tagging & Response Analysis: Tags each objection to the funnel stage where it appears and records how reps currently respond, distinguishing observed outcomes from interpretation. - Root-Cause Diagnosis: Flags objections that signal upstream problems with pricing, positioning, product, qualification, or proof rather than pure sales-handling issues. - Use Case: You have 40 recorded discovery and demo calls and no time to listen through them. Run this Skill to get a ranked objection table with representative quotes, current rep responses, and recommended handling grounded in what appears to work in your own calls. ## Quick Start Analyze all sales call transcripts in this folder and build a ranked objection library with buyer quotes, funnel stages, and recommended responses.

Frequently Asked Questions about objection-library

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build an objection handling document from sales calls?

Gather sales and demo call transcripts across the funnel, then extract each moment a buyer raises a concern or blocker. Normalize duplicate phrasings into single entries, count frequency per call, and capture current rep responses to produce a ranked objection table with recommended handling.

How to analyze sales call transcripts for buyer objections?

Read the full call set and pull every stated question, worry, or flat refusal in the buyer's own words. Tag each objection to its funnel stage, quote the source call, and distinguish observed response outcomes from interpretation before suggesting rebuttals.

What inputs does objection extraction from calls require?

It works from sales and demo call transcripts across discovery through negotiation, plus rep objection notes, lost-deal notes, and support or onboarding calls if pre-sale concerns surface there. A product marketing context file, if present, helps map objections against positioning and competitors.

Can objection frequency be counted when call data is incomplete?

Frequency is only reported when it can be counted reliably from the supplied material. When the evidence does not support a trustworthy count, the limitation is stated explicitly rather than inventing a number.

When is an objection not a sales handling problem?

A recurring objection may indicate upstream issues with product, offer, pricing, positioning, audience fit, qualification, trust, or proof. In those cases the finding is flagged and returned to strategic decision owners instead of being treated as a persuasion problem.