Systems Lab

Agent skill

win-loss-decoder

Turns closed-won and closed-lost deals into ranked, evidence-backed reasons (not rep-selected dropdowns) and routes each pattern to the team that can fix it.

activeSelf-containedInstructions only530 words

Filed under Calls, demos and discovery.

From varunk130/ai-gtm-skill-library · 37 skill entries · 6 · pushed 2026-09-19

What it does when it runs

Turns closed-won and closed-lost deals into ranked, evidence-backed reasons (not rep-selected dropdowns) and routes each pattern to the team that can fix it. Use when: win loss analysis, why did we lose, why do we win, closed lost review, loss reasons, churned deals, competitive losses, buyer interviews.

Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about win-loss-decoder

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/varunk130/ai-gtm-skill-library.git /tmp/ai-gtm-skill-library
git -C /tmp/ai-gtm-skill-library sparse-checkout set "gtm-skills/win-loss-decoder"
mkdir -p ~/.claude/skills/win-loss-decoder
cp -R "/tmp/ai-gtm-skill-library/gtm-skills/win-loss-decoder/." ~/.claude/skills/win-loss-decoder/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from varunk130/ai-gtm-skill-library/blob/158f12c03830dca454576eb1a78b1e4a34ae83e3/gtm-skills/win-loss-decoder/SKILL.md, which is licensed MIT (repository). 530 words, 8 headings.

Win-Loss Decoder (SIGNAL Framework)

CRM loss reasons are picked by the rep in ten seconds, and "price" wins every time. Win-Loss Decoder rebuilds the reason from what the buyer said and did, codes it against a fixed taxonomy, and ranks patterns by revenue so product, marketing, and sales each get the fixes that are theirs.

Core Principle

The buyer's words decide the code. A reason without a quote or artifact from the buyer is logged as "unknown", not guessed.

The SIGNAL Framework

LetterStepThe Question
SSampleWhich deals, and is the sample balanced across wins, losses, segments, and reps?
IInterviewWhat did the buyer say in a 20-minute conversation after the decision?
GGroupWhich taxonomy code does each reason map to?
NNumberHow much ARR sits behind each code, for wins and for losses?
AAssignWhich team owns the fix for each code?
LLoopDid the fix change the rate of that code next quarter?

Reason Taxonomy

CodeCoversDefault owner
VALUEBuyer could not see enough return or urgencyMarketing
FITMissing capability, integration, or compliance needProduct
TRUSTProof, references, security, or vendor-risk concernsMarketing / Security
PROCESSLost the sales process: slow, no champion, wrong buyerSales
PRICEPrice or packaging, after the above are ruled outPricing
STATUS QUOBuyer chose to do nothingMarketing / Sales

Process

  1. Sample - 15-30 recent decisions, at least one-third wins; exclude deals under the ACV floor
  2. Collect - buyer interviews first, then call notes and emails; note the source of every reason
  3. Code - up to two codes per deal (primary, secondary); PRICE only if VALUE and FIT are ruled out
  4. Weight - sum ARR by code for wins and losses; compute loss share - win share per code
  5. Rank - largest positive gap first; these are the reasons you lose more than you win on
  6. Route - one fix per top code, with owner and the metric that will show it worked

Output

Save to outputs/win-loss-decoder-[period]-[YYYY-MM-DD].md

ArtifactDescription
Coded deal logDeal, outcome, codes, quoted evidence, source
Pattern tableCode, ARR won, ARR lost, gap
Fix planTop three codes with owner, action, and target metric

Tips

  1. Interview wins too - you cannot tell a loss pattern from a market pattern without them
  2. Don't let reps interview their own deals - buyers are more candid with a neutral party
  3. Rerun quarterly - the Loop step is where the value compounds

Pairs With

  • deal-xray - PROCESS losses usually show missing proof earlier in the deal
  • competitive-battlecard - competitor-named losses update the battlecard
  • position-lock - persistent VALUE losses signal a positioning problem

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what win-loss-decoder does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.