Menu

Individual skill

leaked-demand-recovery

0upvotes

Use this skill when demand may have leaked between systems: a chat or form lead who never completed a booking, a demo request with no meeting, a call held with no follow-up sent, an inbound reply never answered, a trial that ended quietly, a deal closed lost on a blocker that has since changed. Produces a list of confirmed drops with the evidence attached and one drafted recovery message each, queued for a human to send. Fires on "did they ever book", "who fell through the cracks", "what did we drop", "who never got a follow-up", "unworked inbound", "leads that went nowhere", "recover lost inbound", and before any re-engagement send.

skills/eliezer-cohen/leaked-demand-recovery/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

The cheapest pipeline in any organisation is demand already paid for and then lost in the gap
between two systems. This finds it, proves the drop is real before anyone touches it, and drafts
the recovery.

## The play

1. **Scope the sweep.** Choose the seams to work and the window: about a month for active leaks,
   six to twelve months for closed-lost revival. Confirm the window if one was specified.

2. **Build the candidate list from the capture systems, not the CRM.** The CRM holds what someone
   remembered to log. The mailbox, the calendar, the call recorder and the lead-capture channel
   hold what actually happened. Take the union, deduplicate by person and by company, and include
   people with no CRM record at all: they are the largest silent category and the entire reason to
   build the list this way. `references/leak-map.md` lists the seams worth working and what each is
Back to top