C✳CODEZ.WIN
🌐 English

Localized reading guide

win-loss-reviewPurpose, usage and source

Analyze recently closed opportunities to find patterns in what wins and what loses - stage of loss, common objections from transcripts, deal characteristics. Leader-focused. Use when the user asks "win loss review", "why are we losing deals", "what's working", or "analyze closed opps".

Source retrieved:

Source repository
anthropics/knowledge-work-plugins
SKILL.md
sales/skills/win-loss-review/SKILL.md
Repository stars
34,049
Repository updated
2026-10-30
Categories
Business
Last collected

License: License file needs review

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

Analyze recently closed opportunities to find patterns in what wins and what loses - stage of loss, common objections from transcripts, deal characteristics. Leader-focused. Use when the user asks "win loss review", "why are we losing deals", "what's working", or "analyze closed opps".

How the upstream workflow works

Step 1 - Ground

Check which tools are connected (plus any org facts the user or the project instructions already gave). Ground stage definitions, the loss-reason field (if the org records one), and deal-size bands from the live crm schema and org context (inferred from what is connected or uploaded; if the answer depends on a fact no one has given, ask ONE question, use the answer for this conversation and suggest adding it to the project instructions; otherwise use a clearly labeled default and continue).

Upstream passage · L36 ↗

Step 2 - Pull closed opps

From the CRM: closed opps in scope and period - account (industry, size), stage, amount, close and created dates, lead source, type, owner, won/lost, loss reason where recorded. Plus opportunity history where the CRM exposes it, to find the stage each loss died at.

Upstream passage · L42 ↗

Step 3 - Quantitative patterns

Across the set: win rate overall and by rep, lead source, deal size band, industry, and type (new vs expansion); loss stage distribution (where do losses die?); median cycle length for wins vs losses; median amount for wins vs losses.

Upstream passage · L49 ↗
Upstream passage · ↗
tiers:
  files-only:   quantitative pass from an uploaded closed-opps export
                + pasted transcripts for the qualitative sample
  read-only:    live crm set with history + transcript/email evidence
  gated-writes: none - field backfills hand off to update-opportunity

Requirements and setup

No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d
Source SHA-256
aa991b88dd30c489e404724e37d4cdd74141cb98718cc3c7b7bc555216ffbaed
Back to the full Skill catalog