commitment-tracker

Harvests meeting action items into an aged two-column commitment ledger with evidence verification.

84|37|Updated May 23, 2026
One-click install
npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill commitment-tracker-legioncodeinc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commitment-tracker
Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/main/src/quarantine/skills/keep/commitment-tracker
Command: npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill commitment-tracker-legioncodeinc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Commitments made in meetings disappear because nobody harvests the Action Items blocks that meeting summaries already contain, and nobody checks whether promised deliverables actually happened. This Skill builds a two-column ledger of what you owe and what you are owed from Littlebird meeting summaries, verifies each open item against downstream screen and message evidence, and escalates aging items instead of repeating the same reminder. ## Core Features & Use Cases - Commitment harvesting: Pulls Action Items, Decisions, and Open Questions verbatim from every recorded Littlebird meeting in a window, with owner attribution taken from summary tags rather than error-prone transcripts. - Completion verification: Searches downstream screen snapshots and message threads for the artifact a commitment would have produced, reporting "no evidence it was done" rather than falsely claiming it was not done. - Aging and escalation: Ages items from first commitment date, applies a four-tier escalation ladder that changes channel and framing, and drafts nudges that are held for approval and never sent automatically. - Use Case: Ask "who owes me what" after a month of partnership calls and receive a ledger file showing each open commitment, its age, restatement count, evidence status, and drafted follow-up messages ready for your approval. ## Quick Start Ask the assistant to run commitment-tracker and show everything you promised and everything owed to you over the last 30 days.

Frequently Asked Questions about commitment-tracker

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

FAQPage Schema
How do I track action items from meeting summaries automatically?▼

Run commitment-tracker with a question like "what did I promise" or "who owes me what". It harvests the Action Items blocks from every recorded Littlebird meeting in a 30 or 90 day window, sorts them into owed-by-me and owed-to-me columns, and writes a dated ledger file.

How does the skill verify a commitment was actually completed?▼

It searches for the artifact the commitment would have produced, such as a sent file, a calendar invite, or a later meeting confirming delivery, using search_user_context over messages and screen snapshots. Absence of evidence is reported as "no evidence it was done", never as "it was not done".

Does commitment-tracker require the Littlebird MCP?▼

Yes, the skill requires the Littlebird MCP on a Power or Pro plan and stops immediately if no Littlebird tools are available in the session. Recorded meetings are also required, since unrecorded calendar events are not searchable and are reported as a coverage gap.

Can commitment-tracker send follow-up nudges automatically?▼

No, nudges are drafted but never sent. Before any text reaches another person, the skill presents the item, its evidence, and the full draft verbatim, then asks you to approve, edit, hold, or close the item.

Why does the skill not use transcripts to assign action item owners?▼

Speaker diarization runs at 11 to 13 percent error, so transcript attribution is unreliable. Owner attribution always comes from the summary's tagged Action Items and Decisions blocks, and Unassigned items stay unassigned for the user to claim or discard.

What are the limitations of a meeting commitment ledger?▼

Work done in tools the capture never saw, or confirmed on unrecorded calls, leaves no trace and shows as no evidence. The ledger also cannot detect commitments nobody stated out loud, and it never claims the harvest is complete.