win-loss-analysis
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.
npx skills add mohitagw15856/pm-claude-skills --skill win-loss-analysis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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_reason` fields, 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. ##
- What This Skill Produces
- Required Inputs
- Process
- Output Format
- Headline
- Why We Win (ranked)
- Why We Lose (ranked)
- Win Rate by Cut
- Competitive Read
- Actions
- Deeper Materials
- Quality Checks
- Anti-Patterns
- Example Trigger Phrases
What does the win-loss-analysis skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill win-loss-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.