---
name: broken-promise-audit
description: Find the introductions, documents, and dates you promised in sent mail and never closed, then draft the reopen note.
---

# Broken Promise Audit

**When to use this skill:** Use this skill when the diary is full, the pipeline feels quiet, and you know there are unfinished commitments sitting in sent mail. You are not looking for a new list. You are finishing something you already started.

**How to activate:** Paste this entire skill into Claude, then provide a sent-mail export, pasted threads, or the hit list from a hand search. Claude will run the 14-string hunt, triage, and draft reopen notes. You send them.

---

## Personalization Required

- Access to sent mail from the last twelve months, or a paste of threads you already found.
- The client and referrer names that still matter. If a name is politically dead, say so.
- Whether the user is on Gmail, Outlook, Superhuman, Missive, or HEY, so the search syntax matches.
- Any promise they already closed. Those rows get dropped.

Without a real sent folder or pasted threads, stop and ask for them. Do not invent promises.

---

## What This Skill Produces

A table of open promises: person, company, exact quoted sentence, date sent, days open. A triage of five to ten rows that are cheap to close and still warm. Three reopen drafts that lead with the thing itself, not an apology.

---

## Methodology

### Step 1 : Set the window

Gmail and Superhuman: keep `in:sent newer_than:1y` on every string.

Outlook: open Sent Items first, then search the quoted phrase. Bound with a sent date the user names.

### Step 2 : Run the 14 strings

Hunt in this order. Log hits. Do not read the whole thread yet.

1. Introductions: "I'll introduce", "I will introduce", "happy to introduce", "let me introduce"
2. Connections: "I'll connect you", "put you in touch", "make an intro"
3. Sends: "I'll send", "I'll get that over", "I'll share", "I'll forward"
4. Writing: "I'll put together", "I'll draft", "I'll pull together", "I'll write up"
5. Finding: "I'll dig out", "I'll find that", "I'll look out"
6. Favours: "happy to take a look", "happy to review", "send it over and I'll"
7. The classic: "circle back"
8. Follow-ups: "I'll follow up", "I'll chase", "I'll come back to you"
9. Ball in their court: "ping me", "give me a shout", "let me know when"
10. Named dates: "in the new year", "after the summer", "next quarter", "in a few months"
11. Conditional restarts: "once things settle", "when things calm down", "when the dust settles"
12. Reconnect: "let's reconnect", "let's pick this up", "we should catch up"
13. Open loops: "I'll keep you posted", "I'll let you know", "leave it with me"
14. Where promises die: "no rush", "no urgency", "whenever suits", "no pressure at all"

Run 14 last and read it hardest.

### Step 3 : Log, then triage

Columns: Person, Company, What I promised (quoted exactly), Date sent, Days open, Closed?

Triage on two axes only. How warm is the thread. How cheap is the close. Keep five to ten rows in the cheap-and-warm box.

### Step 4 : Draft the reopen

Rules: no apology in the first line, no "just checking in", no ask in the first message. Deliver the promise.

**Introduction:** subject is the other person's name. Make the intro now.

**The thing you said you'd send:** attach it. No ask.

**The date they gave you:** "You said July." Ask whether the thing is still live.

---

## Hard no

Do not turn the list into a campaign. Do not invent a promise that is not in the thread. Do not search inbound mail and call their half "your promise". This skill only sees what the user wrote. Their leftover-budget line and their "call me in July" live on the other side of the relationship.

---

Nynch is the AI CRM for consultants and fractionals who win on relationships, not spray-and-pray outbound. This skill does one folder, by hand, on your half. Talk to the founder if you want the other half held in memory.