overheard — Claude Code skill: what it does, how to install
overheard scans two weeks of stored memory to surface unfulfilled commitments and prepares followup drafts.
Apache-2.0 ★ 1,497 updated 2026-06-16
npx skills add ghostwright/phantom --skill overheard -a claude-codeWhat overheard does
The skill functions as a promises audit built on top of phantom memory tools. It triggers mcp__phantom-reflective__phantom_memory_search over a 14-day window looking for phrases such as "I will", "let me", "follow up", and merges records by episode identifiers.
It screens out notes directed at yourself and discarded tasks, leaving promises directed at external people. Next, the routine searches memory for signs of completion like confirmation messages or closed topics. If the deadline passed without evidence of follow-through, it highlights three to five unresolved promises and asks whether to compose a draft.
The skill relies strictly on mcp__phantom-reflective__phantom_memory_search and mcp__phantom-reflective__phantom_list_sessions to trace episodes, so without these phantom MCP tools active it cannot discover any commitments.
What it helps with
- detect unresolved conversational commitments across the past 14 days
- verify follow-through on deadlines without scrolling old session logs
- generate suggested followup messages based on your past writing tone
Example prompts for the agent
- Run overheard to check what I promised recently
- What did I commit to in the last two weeks?
- Give me a promises audit and draft followups if needed
How to install overheard
1Skills CLI (Vercel)
npx skills add ghostwright/phantom --skill overheard -a claude-code2Manually: put the files in place
~/.claude/skills/overheard/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/overheard/
1Skills CLI (Vercel)
npx skills add ghostwright/phantom --skill overheard -a codex2Manually: put the files in place
.agents/skills/overheard/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ghostwright/phantom --skill overheard -a cursor2Manually: put the files in place
.cursor/skills/overheard/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ghostwright/phantom skills-builtin/overheard/SKILL.md2Manually: put the files in place
.github/skills/overheard/SKILL.md1Skills CLI (Vercel)
npx skills add ghostwright/phantom --skill overheard -a gemini-cli2Platform CLI
gemini skills install https://github.com/ghostwright/phantom --path skills-builtin/overheardManually: put the files in place
.devin/skills/overheard/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about overheard
How to install overheard in Claude Code?
Run npx skills add ghostwright/phantom --skill overheard -a claude-code in your terminal.
What does the overheard skill do?
It examines conversation history from the past two weeks, flags unfulfilled promises made to others, and surfaces the top three to five overdue items.
Which tools must be configured for overheard to run?
It requires access to mcp__phantom-reflective__phantom_memory_search and mcp__phantom-reflective__phantom_list_sessions.
Source text
SKILL.md · Apache-2.0
---
name: overheard
x-phantom-source: built-in
description: Find commitments the user made in the last two weeks and did not follow through on. A promises audit.
when_to_use: Use when the user says "overheard", "what did I promise", "what am I behind on", "promises audit", "am I dropping balls", "what did I commit to", "what do I owe people", or any similar commitment-check phrase. Also runs automatically once per day at a user-configured time if enabled.
allowed-tools:
- mcp__phantom-reflective__phantom_memory_search
- mcp__phantom-reflective__phantom_list_sessions
context: inline
---
# Overheard: the promises audit
## Goal
Find promises the user made in conversations (in Slack, in email, in messages) that start with phrases like "I'll send", "I will", "let me get back to you", "by Friday", "next week", "I'll follow up", and check whether there is evidence in subsequent memory of follow-through. Surface the gaps as a promises audit, with context for each and a draft action.
The shadow backlog most people carry. The user does not need to be reminded of every forgotten ping; they need the two or three that actually matter.
## Steps
### 1. Pull the last 14 days of memory
Call `mcp__phantom-reflective__phantom_memory_search` with `query: "I will"`, `days_back: 14`, `limit: 30`. Then call it again with `query: "let me"` and merge. Then `query: "follow up"`, and merge. Then `query: "by Friday"` and merge. The merge should deduplicate by episode id.
**Success criteria**: you have a pool of recent episodes that contain commitment language.
### 2. Extract candidate commitments
For each episode, read the detail and pull out phrases where the user was the one making the commitment, not receiving one. Common patterns:
- "I will send you..."
- "Let me get back to you on..."
- "I'll check with <person> and let you know."
- "By Friday I'll have..."
- "Next week I'll..."
- "I'll follow up on..."
Skip commitments that are clearly to yourself, to the agent, or to no one in particular ("I will make more coffee"). Skip commitments that the user has already negated ("I thought I'd send X but actually I'm not going to").
**Success criteria**: you have a list of 5-15 candidate commitments with the original context, who the promise was to (if known), and when it was made.
### 3. Check for follow-through
For each candidate, search memory again for follow-up evidence. The query is a short paraphrase of what was promised. Example: if the commitment was "I'll send Anna the revised doc by Friday", search for "send Anna doc" or "revised doc Anna" with `days_back: 14`.
Evidence of follow-through looks like:
- A later episode where the user clearly sent the thing.
- A later episode where the user explicitly said it was done.
- A later episode where someone thanked the user for the thing.
- A later episode where the topic was closed ("we decided to cancel that").
If none of those are present and the commitment's stated deadline has passed or is about to pass, it is an open promise.
**Success criteria**: you have classified each candidate as "done", "open", or "unclear".
### 4. Surface the top 3-5 open promises
Pick the most important open promises. "Most important" means:
- The recipient is a known person (not "someone in the channel").
- The deadline is past or within 24 hours.
- It has not been renegotiated.
- It is the kind of thing that matters if it drops (a deliverable, a followup, a decision).
Skip low-stakes promises ("I'll check", "I'll think about it") unless they are the only ones open.
Render each as:
> **To Anna, committed Tuesday.** You said you would send the revised pricing doc "by Friday." I do not see evidence in memory that it has been sent. Three days overdue. Want me to draft the followup?
**Success criteria**: under 400 words total, 3-5 open promises, each anchored to a specific memory episode, each ending with a concrete next-step offer.
### 5. Offer to draft followups
For each open promise, offer to draft the followup message in the user's voice. Do not draft until the user says yes. When the user says yes, pull a few recent messages from memory that show the user's tone, then write the draft as a suggestion.
**Success criteria**: the user either says "yes draft those" or "no I've got it". Either is fine. Do not force the draft.
## Rules
- Never moralize about broken commitments. The tone is "here is what I saw", not "here is what you should do".
- Never em-dash.
- Never surface more than five open promises. Density beats coverage.
- Never fabricate a recipient. If you cannot tell who the promise was to, say "to someone in <channel>" and let the user fill in the gap.
- Always anchor each promise to a real memory episode.
- Always offer the followup draft, but never send it without explicit approval.
© ghostwright · Apache-2.0 · ghostwright/phantom