track-my-promises

Extract time-bound promises from replies and drafts into tracked followups.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/akiotanaka847/qaio-desktop --skill track-my-promises
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: track-my-promises
Source: https://github.com/akiotanaka847/qaio-desktop/tree/main/store/agents/support/.agents/skills/track-my-promises
Command: npx skills add https://github.com/akiotanaka847/qaio-desktop --skill track-my-promises

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Customers often hear a commitment with a deadline, but the follow-through can get lost unless it is captured and tracked. Track My Promises turns those time-bound promises into durable followups so deadlines surface in your morning brief.

Core Features & Use Cases

  • Promise extraction from your messages/drafts: Detects time-bound language like “I’ll X by Y” and records the exact wording you wrote.
  • Due date parsing with ambiguity handling: Converts explicit dates and relative timeframes into a normalized deadline, and assigns a default when the date is vague.
  • Conversation-linked followups and notes: Appends followup records to a followups store and mirrors them as dated lines in the relevant conversation notes, cancelling superseded conflicting promises when needed.
  • Support workflow fit: Best for support agents who routinely commit to turnaround times and want automatic tracking against the thread/customer context.

Quick Start

Tell the agent: “I’ll email the updated contract to Acme by Friday EOD.”

Frequently Asked Questions about track-my-promises

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

FAQPage Schema
How do I track customer deadlines mentioned in support threads?

Promise extraction detects time-bound language like 'I'll X by Y' in your support thread replies and drafts, records the exact wording, and converts the timeframe into a normalized deadline for followup tracking.

How do I parse vague or relative due dates from customer communication into a standard format?

Due date parsing converts explicit dates and relative timeframes from your conversation drafts into normalized ISO-8601 UTC deadlines, assigning a default deadline when the date language remains vague.

Can I automatically cancel conflicting open followups when a new promise is made?

Yes, when new time-bound commitments are tracked, the Skill atomically appends new followup records while cancelling superseded conflicting open followups and mirroring entries into conversation notes.

Does deadline tracking for support threads work without external dependencies?

Yes, this Skill functions without external dependencies, parsing time-bound commitments from your support thread drafts and managing the resulting followup records internally.

What is the best way to ensure time-bound commitments are not missed in customer communication?

The best way to prevent missed follow-through is to automatically extract time-bound promises from your replies, parse them into ISO-8601 UTC deadlines, and surface them as dated lines in daily briefings and conversation notes.