win-loss-analysis SKILL.md skillA
win-loss-analysis from prosyo-ai/gtm-skill is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add prosyo-ai/gtm-skill/win-loss-analysis@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- prosyo-ai/gtm-skill
- Path
plugin/skills/win-loss-analysis/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 23, 2026
- Size
- 3,924 bytes
- Repository stars
- 12
- License
- MIT
Use this skill when you want to learn why deals are won and lost: "run a win-loss analysis", "why are we losing to competitor X", "analyse last quarter's closed deals", "prepare win-loss interviews". Analyses closed-won and closed-lost deals and buyer interviews, separates stated reasons from real ones, finds patterns by segment, competitor, deal size and stage, and turns them into specific changes for targeting, messaging, product and sales process.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
Use this quarterly or after a run of losses. It replaces anecdotes ("we always lose on price") with patterns and specific changes.
## Inputs
- Closed-won and closed-lost deals for the period with stage lost, reason, competitor, amount, segment and cycle length.
- Call notes, emails and, ideally, 5-10 buyer interviews.
- Rep notes on why they think deals went the way they did.
## The play
### 1. Quantify first
Win rate by segment, deal size, lead source, competitor, rep and stage lost. The stage where deals die says more than the reason field: losses after the demo are fit or value problems; losses after the proposal are price, champion or competitor problems.
### 2. Separate stated from real reasons
"Price" is the most common stated reason and often not the real one. Look for evidence: was the economic buyer engaged? Was value quantified? Did the champion go quiet? Real reasons usually fall into: no quantified value, wrong buyer, competitor better fit, poor timing, weak process, product gap.
### 3. Interview buyers
Short calls with won and lost buyers, run by someone other than the rep. Ask about their process and alternatives, not about the rep. A guide:
…Read the whole file at its exact version.
How to install
mdr add prosyo-ai/gtm-skill/win-loss-analysis@sha256:3aa8debd4b32450cThe line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_hqinzlbk5munsdaa)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 23, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3924 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
prosyo-ai/gtm-skill · 12 stars · license MIT · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hqinzlbk5munsdaa GET https://markdownregistry.com/api/v1/resolve?ref=prosyo-ai/gtm-skill/win-loss-analysis GET https://markdownregistry.com/api/v1/blob/3aa8debd4b32450cdcf8db93a4c09c051959ec7cea8d9c5307dd8cbd4b0c0636
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from prosyo-ai/gtm-skill
Every file in prosyo-ai/gtm-skill