arrows-win-loss-analysis SKILL.md skillB
arrows-win-loss-analysis from arrowshq/arrows-sales-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add arrowshq/arrows-sales-skills/arrows-win-loss-analysis@git:20261021.d3cd147Pins git:20261021.d3cd147 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- arrowshq/arrows-sales-skills
- Path
plugins/arrows-sales-skills/skills/arrows-win-loss-analysis/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261021.d3cd147, committed Oct 21, 2026
- Size
- 57,369 bytes
- Repository stars
- 5
- License
- Apache-2.0
Win-loss analysis from Sales Skills by Arrows. A deep read of closed deals (every won and lost deal counted, about 25 wins and 25 losses read end to end, call transcripts and email) that answers why the team wins and why it loses: which segments win (size, source, industry, new vs. existing customers), the 3–5 moves that show up on wins and not on losses (with counts on both sides) and what's noise, where and why deals really die compared with what the CRM says, who was missing from the buying…
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
Answers one question from the team's own closed deals: **why do we win, and why do we lose?** Every number comes from their CRM, calls and email, with the counts on both sides, so it's clear what actually separates a win from a loss. | Section | What it answers | |---|---| | Three things to change this quarter | The changes most likely to raise the win rate, each with the evidence and steps | | Who wins | Win rate by segment: company size, lead source, industry, the buyer's current tools, existing customers vs. new | | The moves that win | The 3–5 things that happen on wins and not on losses, counted on both sides, plus what every deal gets that doesn't decide anything | | Where and why deals die | The stage and timing where losses happen, and the real loss reasons from reading the deals compared with what the CRM says | | The buying group | Which roles were involved on wins and who was missing on losses | | Methodology | Which parts of the team's methodology (MEDDPICC, SPICED, BANT or their own) actually predict a win | | By rep (leaders) | Each rep's win rate and cycle, and what the top rep does that the others don't | …
Read the whole file at its exact version.
How to install
mdr add arrowshq/arrows-sales-skills/arrows-win-loss-analysis@sha256:7604fbfd91b94b4aThe line at the top of this page pins the label git:20261021.d3cd147, 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_5tucg3csc2yhou2n)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 21, 2026.
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (57369 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
arrowshq/arrows-sales-skills · 5 stars · license Apache-2.0 · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5tucg3csc2yhou2n GET https://markdownregistry.com/api/v1/resolve?ref=arrowshq/arrows-sales-skills/arrows-win-loss-analysis GET https://markdownregistry.com/api/v1/blob/7604fbfd91b94b4afe503d80f447615ee2db9568044a994f0779c10e75a57aa2
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 arrowshq/arrows-sales-skills
Every file in arrowshq/arrows-sales-skills