ClaudeSuperPower

objection-blocker-tracker

Skill

Track the open objections and blockers on a deal and how they have evolved across recent calls. Uses conversation_intelligence over an account's or contact's recent engagements. Identify the account or contact by ZoomInfo ID (preferred) or name (triggers a lookup). Use when someone asks "what object

Install

git clone https://github.com/Zoominfo/zoominfo-mcp-plugin.git ~/.claude/skills/objection-blocker-tracker

What is objection-blocker-tracker?

Track the open objections and blockers on a deal and how they have evolved across recent calls. Uses conversation_intelligence over an account's or contact's recent engagements. Identify the account or contact by ZoomInfo ID (preferred) or name (triggers a lookup). Use when someone asks "what objections are still open with Acme", "what's blocking this deal", "how has the security concern evolved", or wants a blocker check before a forecast or a next call. Reasons over the last few engagements only, so it tracks recent movement rather than full deal history.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~141 tokens of context used while enabled, before you invoke anything

Documentation

README · ~2 min read

Objection & Blocker Tracker

Surface the concerns standing between you and the deal, and show whether each is getting better or worse.

Prerequisites

conversation_intelligence requires at least one connected meeting or email source and consumes AI credits. browse_engagements (to scope or pick calls) requires an active integration and is free. If no conversation data exists, say so rather than reporting "no objections" (the absence of data is not the absence of objections).

Input

Provided via $ARGUMENTS:

  • Scope (required) — an account or contact (ZoomInfo ID, or a name to resolve).
  • Focus (optional) — e.g. "just pricing", "anything technical", "security and procurement". Narrows the read.

Workflow

  1. Resolve scope. If no account or contact was supplied, ask the user which one before proceeding. Use a ZoomInfo ID directly, or resolve a name via search_companies / search_contacts.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills