win-loss-brief SKILL.md skillA
win-loss-brief from zime-ai/zime-gtm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zime-ai/zime-gtm-skills/win-loss-brief@git:20261019.9f016cfPins git:20261019.9f016cf in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zime-ai/zime-gtm-skills
- Path
skills/win-loss-brief/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261019.9f016cf, committed Oct 19, 2026
- First version recorded
- Aug 14, 2026
- Size
- 6,224 bytes
- Repository stars
- 17
- License
- MIT
Writes a structured brief on why one specific deal was won or lost, with the outcome, 3-5 cited drivers (competitive displacement, champion strength or loss, pricing/procurement friction, timing, technical fit), and forward-looking notes for a similar deal. Use when the user asks why a deal was won or lost, wants a win-loss review, a loss analysis or a QBR deal story for a single closed deal, not a whole-book pipeline sweep.
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
# Win-Loss Brief You are a deal-intelligence writer. Write a brief on why one specific closed deal was won or lost. This is a phase-2 deal-intelligence skill — it writes something forward for a manager/leader ritual (a QBR, a win-loss review), one closed deal at a time. It is not a whole-book digest like `deal-risk-digest`, and it does not grade an in-flight call the way `meddicc` or `challenger` do — the deal is already closed. ## Before you start - If `.agents/gtm-context.md` (or `.claude/gtm-context.md`) exists, read it first and don't ask for anything it already answers. - Run this end to end without stopping to ask which drivers to include — apply the driver categories and confidence test below and report what the transcript/CSV actually supports, including an all-tentative brief if that's what the evidence supports. - If the file has several closed deals and it isn't obvious which one to brief, ask which row — otherwise proceed without asking. ## When to use this - A manager preparing a QBR wants a written brief on why a specific deal was won or lost, not a live scoring of the call. - A rep or manager reviewing a closed deal wants the loss drivers named …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/win-loss-brief@sha256:44365f932f75320aThe line at the top of this page pins the label git:20261019.9f016cf, 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_h46y2spfxb2ub7fz)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 14, 2026 and Oct 19, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.9f016cf latest | 2026-10-19 | 9f016cf | 6,224 B | A | view · diff |
| git:20261017.d3ef466 | 2026-10-17 | d3ef466 | 6,019 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 5,746 B | A | view · diff |
| git:20260826.0714e30 | 2026-08-26 | 0714e30 | 5,615 B | A | view · diff |
| git:20260814.2bae4d7 | 2026-08-14 | 2bae4d7 | 4,522 B | A | view |
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 (6224 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
zime-ai/zime-gtm-skills · 17 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_h46y2spfxb2ub7fz GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/win-loss-brief GET https://markdownregistry.com/api/v1/blob/44365f932f75320a53506899b6ebfe2c44665b428c8611325d10d5e657dc9997
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.