Deal Desk
alirezarezvani/claude-skills
A skill your agent uses when reviewing a specific inbound deal before close — when sales has asked for a discount that exceeds AE authority, when the customer has redlined the MSA, when per-deal…
Analyze why deals are won and lost and turn it into an action plan.
MITAuto-check passed
Install Win Loss Analysis
$ npx skills add mohitagw15856/pm-claude-skills --skill win-loss-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills win-loss-analysis --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/win-loss-analysis .claude/skills/win-loss-analysis && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "win-loss-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/win-loss-analysis into .claude/skills/win-loss-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "win-loss-analysis", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/win-loss-analysisType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill win-loss-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills win-loss-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/win-loss-analysis .agents/skills/win-loss-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "win-loss-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/win-loss-analysis into .agents/skills/win-loss-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "win-loss-analysis", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill win-loss-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills win-loss-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/win-loss-analysis .cursor/skills/win-loss-analysis && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "win-loss-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/win-loss-analysis into .cursor/skills/win-loss-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "win-loss-analysis", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/win-loss-analysis--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill win-loss-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills win-loss-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/win-loss-analysis .gemini/skills/win-loss-analysis && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "win-loss-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/win-loss-analysis into .gemini/skills/win-loss-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "win-loss-analysis", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills win-loss-analysisInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill win-loss-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/win-loss-analysis .github/skills/win-loss-analysis && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "win-loss-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/win-loss-analysis into .github/skills/win-loss-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "win-loss-analysis", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill win-loss-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills win-loss-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/win-loss-analysis .opencode/skills/win-loss-analysis && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "win-loss-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/win-loss-analysis into .opencode/skills/win-loss-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "win-loss-analysis", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
win-loss-analysis- GitHub stars
- 1.4k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 582 words
- Files
- 2 (incl. references)
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyze why deals are won and lost and turn it into an action plan.
- Works in 6 steps: Normalize the reasons — collapse… → Quantify — count wins and losses per… → Separate controllable from structural —… → …
- Asked to run a win/loss analysis
- SKILL.md covers What This Skill Produces, Required Inputs, Process and Output Format, plus 10 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Win Loss Analysis is an agent skill from mohitagw15856/pm-claude-skills. Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/buyer-interview-craft.md`).
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to run a win/loss analysis
- Review closed-won and closed-lost deals
- Understand why the team is losing to a competitor
- Summarize sales feedback into patterns
Example prompts
- “/win-loss-analysis”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Normalize the reasons — collapse free-text loss reasons into a consistent taxonomy (price, product gap, timing/no-decision, competitor…
- Quantify — count wins and losses per reason; weight by deal value; compute win rate overall and by cut.
- Separate controllable from structural — a missing feature is controllable; a genuine no-budget is not. Focus action on the controllable.
- Pull evidence — attach 1–2 real quotes per major theme. Never fabricate quotes; mark [quote to add] if none is available.
- Isolate competitor dynamics — where you lose to each competitor and on what basis.
- Recommend actions — for each top theme, the single highest-leverage move and who owns it.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Win Loss Analysis loads about 1.2k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 110 tokens; SKILL.md has 582 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 582 words, ~1,178 tokens.
Download SKILL.mdSave it as
.claude/skills/win-loss-analysis/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- win-loss-analysis
- description
- Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
Win/Loss Analysis Skill
Turn raw deal outcomes and buyer feedback into a clear picture of why you win and lose — and what to do about it. The output should let a product marketer or revenue leader act on patterns, not anecdotes.
What This Skill Produces
- A win/loss report with the top reasons deals were won and lost, ranked by frequency and deal value
- Win/loss rates cut by segment, deal size, competitor, and source where the data allows
- Representative buyer quotes that make each theme concrete
- A prioritized action list mapped to product, marketing, sales, and pricing owners
Required Inputs
Ask for these if not provided:
- Deal data — a list of closed-won and closed-lost deals, ideally with amount, segment, competitor, and stage lost
- Feedback source — win/loss interview notes, CRM
closed_lost_reasonfields, survey responses, or call transcripts - Time window and any segmentation you care about (segment, region, product line)
- Primary competitors to track explicitly
- The decision this feeds — a QBR, a roadmap review, a messaging refresh, an enablement push
If the data is thin, say so and analyze what exists rather than inventing outcomes.
Process
- Normalize the reasons — collapse free-text loss reasons into a consistent taxonomy (price, product gap, timing/no-decision, competitor, champion left, poor fit, etc.).
- Quantify — count wins and losses per reason; weight by deal value; compute win rate overall and by cut.
- Separate controllable from structural — a missing feature is controllable; a genuine no-budget is not. Focus action on the controllable.
- Pull evidence — attach 1–2 real quotes per major theme. Never fabricate quotes; mark
[quote to add]if none is available. - Isolate competitor dynamics — where you lose to each competitor and on what basis.
- Recommend actions — for each top theme, the single highest-leverage move and who owns it.
Output Format
Win/Loss Analysis — [Period]
Scope: [N won · N lost · total value] · Segments: [list] · Source: [interviews / CRM / survey]
Headline
[2–3 sentences: overall win rate, the biggest swing factor, and the one thing to fix first.]
Why We Win (ranked)
| # | Reason | % of wins | Notable in |
|---|---|---|---|
| 1 | [Reason] | [%] | [segment/competitor] |
Evidence: "[buyer quote]"
Show full SKILL.md (238 more words)Show less
Why We Lose (ranked)
| # | Reason | % of losses | Controllable? | Est. value at stake |
|---|---|---|---|---|
| 1 | [Reason] | [%] | Yes/No/Partly | [$] |
Evidence: "[buyer quote]"
Win Rate by Cut
| Cut | Win rate | Read |
|---|---|---|
| [Segment / competitor / deal size] | [%] | [what it means] |
Competitive Read
- vs [Competitor]: [where and why we win/lose, and the counter]
Actions
| Theme | Recommended action | Owner | Effort | Expected impact |
|---|---|---|---|---|
| [Theme] | [Specific move] | [Product/PMM/Sales] | S/M/L | [win-rate or deal-value effect] |
Deeper Materials
references/buyer-interview-craft.md— the interview craft that defeats buyer politeness — who calls, when, and the questions that get truth
Quality Checks
- Every reason is backed by counts, not vibes
- Losses are split into controllable vs structural
- Each major theme has a real quote or an explicit
[quote to add] - Actions name an owner and the highest-leverage single move
- Competitor findings are specific enough to change a battlecard
Anti-Patterns
- Do not treat "price" as a root cause without checking whether it's really value perception
- Do not average away segment differences — a 60% overall win rate can hide a 20% enterprise rate
- Do not fabricate buyer quotes or inflate sample size; state the n
- Do not list 15 actions — rank ruthlessly and name the top few
- Do not blame sales or product reflexively; let the data assign the theme
Example Trigger Phrases
- "Run a win/loss analysis on last quarter's closed deals"
- "Why are we losing enterprise deals to [Competitor]?"
- "Summarize these win/loss interviews into themes and actions"
- "Turn our CRM closed-lost reasons into a report for the QBR"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/win-loss-analysis of mohitagw15856/pm-claude-skills.
- SKILL.md
- references/buyer-interview-craft.md
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Win Loss Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Win Loss Analysis this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Deal Deskalirezarezvani/claude-skills | 28k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Win Loss AnalysisTheCraigHewitt/skills | 157 | — | ~5.8k | Automated safety check: Pass | MIT | |
| Lost Deal Revival AgentOthmane-Khadri/YALC-the-GTM-operating-system | 317 | — | ~3k | Automated safety check: Pass | MIT | |
| Data Loss Gategarrytan/gbrain | 31k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Recipe Log Deal Updategoogleworkspace/cli | 31k | — | ~234 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Win Loss Analysis
TheCraigHewitt/skills
When the user wants to analyze why deals were won or lost, find patterns across closed deals, or extract competitive intelligence from deal outcomes.
Lost Deal Revival Agent
Othmane-Khadri/YALC-the-GTM-operating-system
Drafts revival messages for closed-lost deals when a public company signal contradicts the original objection.
Data Loss Gate
garrytan/gbrain
Confirmation gate before any bulk delete, cleanup, or destructive operation that could result in data loss — shell-level (rm -rf, git rm, bulk sed) or brain-level (bulk forget, delete sweeps…
Recipe Log Deal Update
googleworkspace/cli
Append a deal status update to a Google Sheets sales tracking spreadsheet.
Won Deal Icp Finder
swan-gtm/gtm-skills
A skill your agent uses when someone wants to know who actually pays them — auditing closed-won deals to derive a proven ideal customer profile instead of an aspirational one, then building a…
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Win Loss Analysis
What does Win Loss Analysis do?
Analyze why deals are won and lost and turn it into an action plan. Win Loss Analysis is an agent skill from mohitagw15856/pm-claude-skills. Analyze why deals are won and lost and turn it into an action plan.
When should I use Win Loss Analysis?
Win Loss Analysis fits situations like: asked to run a win/loss analysis; review closed-won and closed-lost deals; understand why the team is losing to a competitor; summarize sales feedback into patterns.
How do I install Win Loss Analysis in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill win-loss-analysis -a claude-code`. Or copy the skill folder (skills/win-loss-analysis in mohitagw15856/pm-claude-skills) into .claude/skills/win-loss-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Win Loss Analysis in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill win-loss-analysis -a codex`. Or copy the skill folder (skills/win-loss-analysis in mohitagw15856/pm-claude-skills) into .agents/skills/win-loss-analysis in your project. Codex loads it when a task matches its description.
Can I use Win Loss Analysis in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill win-loss-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/win-loss-analysis, .gemini/skills/win-loss-analysis, .github/skills/win-loss-analysis and .opencode/skills/win-loss-analysis in your project.
What does Win Loss Analysis need to run?
SKILL.md names no scripts, command-line tools or credentials: Win Loss Analysis is instructions for the agent only.
Does Win Loss Analysis access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Win Loss Analysis safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Win Loss Analysis use?
Win Loss Analysis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Win Loss Analysis use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 565 tokens, read only when the agent opens those files.
What are the alternatives to Win Loss Analysis?
Skills that share tags, products or a category with Win Loss Analysis: Deal Desk (alirezarezvani/claude-skills, 28k stars), Win Loss Analysis (TheCraigHewitt/skills, 157 stars), Lost Deal Revival Agent (Othmane-Khadri/YALC-the-GTM-operating-system, 317 stars) and Data Loss Gate (garrytan/gbrain, 31k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Win Loss Analysis?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,433 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 8, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.