Borrowing it
Nothing to install: this file belongs to Othmane-Khadri/YALC-the-GTM-operating-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Othmane-Khadri/YALC-the-GTM-operating-system/main/.claude/skills/lost-deal-revival-agent/SKILL.mdgit clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-systemWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/lost-deal-revival-agent)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/lost-deal-revival-agent"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/lost-deal-revival-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/lost-deal-revival-agent"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/lost-deal-revival-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00174 | $0.03071 |
| Opus 5.5 | $0.00070 | $0.01228 |
| Sonnet 5.5 | $0.00035 | $0.00614 |
| Haiku 4.5 | $0.00017 | $0.00307 |
Grade A, and why
lost-deal-revival-agent scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lost Deal Revival Agent
Receives signal-pair fire payloads from the signal-pair watcher
(src/lib/agents/signal-pair-watcher.ts) when a watched company has both
a Claap-derived closed-lost objection tag and a fresh PredictLeads signal
within a 14-day window. Fetches the verbatim Claap objection quote,
drafts a tight 2-line revival message that quotes the objection back and
names the new signal change, then writes the draft to one of two
operator-chosen output targets for human review.
You produce drafts. You do NOT send messages. You do NOT start Lemlist campaigns. You do NOT modify Claap recordings.
When This Skill Applies
- "revive closed-lost deals"
- "set up revival agent"
- "when objection X is fixed by signal Y reach out"
- "lost deal revival"
- "closed-lost re-engagement loop"
NOT this skill:
- "send a cold email" → use
email-sequence/send-cold-email - "launch a LinkedIn campaign" → use
launch-linkedin-campaign - "summarize this Claap call" → use Claap's own per-call summary
When invoked from Slack
If the invocation prompt mentions a Slack channel and thread, treat THAT Slack thread as your output surface instead of the chat. The drafted revival message and any progress notes go to the thread instead of the chat.
- Every progress message goes to the Slack thread via the Slack MCP (registered as
slack). Use the toolslack_post_messagewith the channel and, when a thread timestamp is present, the samethread_ts(orslack_reply_to_threadfor thread replies) so updates land in the same thread. There is no native message-update tool, so post a new message rather than trying to edit an existing one. - Any approval gate (this skill defaults to producing a draft for human review, but if the invocation introduces a confirm-before-write step) is posted to the Slack thread as a short, structured preview, then you wait for either a thumbs-up reaction OR a thread reply matching
approve | ship it | looks good | go | yesFROM THE ORIGINAL REQUESTER ONLY (the user id named in the invocation prompt). Poll for the reply withslack_get_thread_repliesand useslack_add_reactionto acknowledge receipt. Ignore approvals from anyone other than the original requester. No one else can approve on their behalf. - The final result goes back to the thread with any artifact URLs (HubSpot task, Lemlist DRAFT campaign).
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 283 lines · 174 tokens per session scan A 4e1dd8ef5ec9
lost-deal-revival-agent is a skill published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (323 stars, last pushed 2mo ago), licensed MIT. It adds 174 tokens to every session and 3,071 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
toflow-create-sequence
Build a multi-channel outreach sequence in toflow.ai (email, LinkedIn, WhatsApp) and enroll people into it. Use this whenever the user asks to create, set up, or launch a sequence, campaign, or drip/outreach flow, or to enroll a person/list into one.
toflow-prospect-and-list
Search LinkedIn for prospects with Sales Navigator-style filters, pull people from existing connections or post engagement, set up a signal agent to monitor for new prospects automatically, and organize results into lists and saved views. Use this whenever the user wants to find new people/companies to target, or…
toflow-enrich-contacts
Find verified emails and phone numbers for people in the CRM, one at a time or in bulk across a list, or run a custom AI enrichment to derive a field from available data. Use this before enrolling someone in an email sequence, or whenever contact data is missing, unverified, or needs AI-derived research.
toflow-manage-crm
Create, search, and update CRM records (people, companies, deals), manage custom attributes, categories, and deal pipelines. Use this whenever the user wants to look up, add, or edit CRM data, or manage a deal's pipeline stage.
toflow-manage-conversations
Send LinkedIn connection requests, direct messages, and premium/InMail-style messages, send WhatsApp messages, and manage connected messaging accounts and threads. Use this for one-off LinkedIn/WhatsApp outreach outside of a sequence.
toflow-manage-email
Read, draft, send, reply to, and forward emails from connected toflow.ai sending accounts, and check open-tracking and engagement stats. Use this for one-off emails outside of a sequence, or to manage an existing email thread or draft.