ClaudeSuperPower
SubmitLog in

commitment-ledger

Skill

Build a ledger of what we promised versus what they promised, and what is still outstanding, across the last few engagements with an account or contact. Uses conversation_intelligence as the primary source. Identify the account or contact by ZoomInfo ID (preferred) or name (triggers a lookup), or po

0Finance

Install

git clone https://github.com/Zoominfo/zoominfo-mcp-plugin.git ~/.claude/skills/commitment-ledger

What is commitment-ledger?

Build a ledger of what we promised versus what they promised, and what is still outstanding, across the last few engagements with an account or contact. Uses conversation_intelligence as the primary source. Identify the account or contact by ZoomInfo ID (preferred) or name (triggers a lookup), or point it at specific calls. Use when someone asks "what did we commit to", "what are they supposed to send us", "what's still outstanding with this account", or wants an accountability check before a follow-up. Covers the last few engagements only, not full 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

Commitment Ledger

A two-sided accounting of promises across recent conversations: ours, theirs, and what is still open.

Prerequisites

conversation_intelligence requires at least one connected email or meeting source and consumes AI credits. browse_engagements (used to scope or pick engagements) requires an active integration and is free. If no conversation data exists, say so rather than presenting an empty ledger as "no commitments".

Input

Provided via $ARGUMENTS:

  • Scope (required) — an account (company ID or name/domain), a contact (contact ID or name + company), or specific calls to review.
  • Emphasis (optional) — e.g. "just what they owe us", "anything tied to the contract". Shapes the output.

Workflow

  1. Resolve scope. Use a ZoomInfo ID directly, or resolve a name via search_companies / search_contacts. If the user wants specific calls and none are named, present a browse_engagements shortlist to pick from before spending credits.

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.