Read the whole relationship at a glance.
Puts meetings, replies, and sequence activity on one timeline and flags the moment a champion goes dark.
Inside: The relationship timeline and the champion-drop detector.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
meeting history, email reply timelines, and sequence enrollments, live. It sees conversations the CRM never logged.
the logged activity layer, contact roles, and account context.
Swapping tools is a matter of pointing the two roles at different connectors. If your CRM names the primary-contact flag differently, set the champion field to match.
| Set this | What it is | Default / Example |
|---|---|---|
| Meeting tool | The connector for meeting + email + sequence history | Any meeting/conversation platform |
| CRM | The connector for activity sync, contact roles, account context | Any CRM |
| Champion field | The CRM field that marks the primary contact on a deal | Primary contact role flag |
| Dark-days threshold | Days of silence before a contact is flagged dropped off | 21 days |
Everything the skill does, in full.
This skill turns the scattered history of a relationship into one readable pulse. It pulls meetings, email replies, and sequence activity, lays them on a timeline, tracks who is still replying and who has gone quiet, flags when a champion drops off, summarizes recent meetings, and drafts a grounded follow-up. It answers the question you ask before you reach out: what has actually been said, and where did we leave off.
- 11. Meeting timeline. The last 90 days of meetings: date, type, attendees, topics, decisions, action items with owner and status.
- Email reply tracking. Per contact: last reply date, reply count in the window, baseline cadence. Compare current behavior to baseline.
- Last positive signal. The most recent forward-moving reply or commitment across all contacts.
- Champion drop-off detection (locked rule below).
- Sequence enrollment. Active sequences, touches delivered, reply state.
- Pulse summary. A short read of the relationship's current state.
- Suggested next move. The contact, the action, and the open commitments to close.
- Cross-source completeness. The skill never reports "no activity" from a single source. It cross-references meeting-tool meetings and emails, CRM tasks and events, and any email thread context.
- Champion drop-off, locked rule. A primary contact is flagged "dropped off" only when their last reply is older than the dark-days threshold AND they have at least 3 historical replies in the prior 90 days. Without that baseline the skill says the signal is insufficient. This prevents flagging a brand-new contact who never replied.
- Meeting digest quality. Every digest names attendees, topics, decisions, action items with owner and deadline, and open questions. If a meeting has no transcript, the skill says so rather than fabricating.
NORTHWIND, Conversation Pulse · last 90 days
Source: meeting tool + CRM activity layer
Meeting timeline
May 27, Renewal touchbase, Rep + Primary Contact, 30 min
Decisions: confirmed June 15 renewal date
Action: Rep to send SOW by May 30 (sent May 29)
May 12, QBR, Rep + Primary Contact + Finance Lead, 60 min
Action: Primary Contact to share rollout plan (open, 17 days)
Email cadence
Primary Contact: last reply yesterday, 6 in 7 days, baseline 1-2/wk, HEALTHY
Finance Lead: last reply 12 days ago, baseline weekly, SLOWING
Former Champion: last reply 47 days ago, 8 historical replies, DROPPED OFF
Suggested next move
Rep: 1:1 with Former Champion by Friday, reference past advocacy
Open commitments: Primary Contact's rollout plan (17 days open)Defaults tuned for a typical B2B cadence: a 90-day window, a 21-day dark threshold, and a 3-reply baseline minimum below which "dropped off" has no meaning. Widen the window for slow enterprise cycles, tighten the dark threshold for high-velocity motions, and raise the baseline if your contacts reply often. Re-tune the window and the dark threshold to your sales cycle before trusting the drop-off flags.
Where an operator takes this next.
The read is step one. Here's where an operator takes it once the manual version proves out.
You built the read once; now it runs itself.
Point a scheduled Claude task at your meeting tool and CRM weekly and flag any champion crossing the dark-days threshold before the renewal conversation.
DM the account owner in Slack the moment a champion drop-off fires, instead of surfacing it at the next QBR prep.
Hand the pulse straight to comms-agent so the drafted follow-up ships as a real email draft, not a copy-paste step.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.