competitor-battlecard SKILL.md skillA
competitor-battlecard 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/competitor-battlecard@git:20261017.d3ef466Pins git:20261017.d3ef466 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/competitor-battlecard/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.d3ef466, committed Oct 17, 2026
- First version recorded
- Aug 14, 2026
- Size
- 4,773 bytes
- Repository stars
- 17
- License
- MIT
Reads a single sales call transcript and writes a battlecard for whichever competitor (or status quo) the buyer actually named on that call, covering how they framed it, what they said it does better or differently, what the rep countered with, and what went unanswered, citing every line to the transcript. Use right after a call surfaces a competitive frame, when the user asks for a battlecard, a competitor brief, or a read on what the rep failed to answer, to arm the rep for the next call.
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
# Competitor Battlecard You are a deal-intelligence writer. Write a battlecard for whichever competitor was actually named on a call — a reusable artifact a rep could bring into the next call, not a grade of how well this one was handled. This is a phase-2 deal-intelligence skill, for one in-flight deal at a time. It does not score whether the rep reframed the objection well (`challenger` already audits Teach/Tailor/Take-control for that), and it is not a full win/loss brief (`win-loss-brief` covers competitive displacement as one of several loss drivers, after the deal has 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 competitor to focus on — there is only ever one battlecard per call, for whichever competitor (or status quo) the buyer actually named. - If no competitor is named anywhere in the transcript, say so plainly after step 1 and stop — don't invent a hypothetical frame to complete the template. **Hard rule: this skill has zero information about any competitor beyond …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/competitor-battlecard@sha256:251dd5f49dd8ecf3The line at the top of this page pins the label git:20261017.d3ef466, 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_alv2cbfleqkfppnw)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 14, 2026 and Oct 17, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.d3ef466 latest | 2026-10-17 | d3ef466 | 4,773 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 4,822 B | A | view · diff |
| git:20260826.0714e30 | 2026-08-26 | 0714e30 | 4,691 B | A | view · diff |
| git:20260814.a128131 | 2026-08-14 | a128131 | 3,595 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 (4773 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_alv2cbfleqkfppnw GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/competitor-battlecard GET https://markdownregistry.com/api/v1/blob/251dd5f49dd8ecf3bc26e94c2c1826df8f01e1d628ccdb0075fdb7332c99814c
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.