deal-highlights SKILL.md skillA
deal-highlights 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/deal-highlights@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/deal-highlights/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.d3ef466, committed Oct 17, 2026
- First version recorded
- Aug 14, 2026
- Size
- 4,094 bytes
- Repository stars
- 17
- License
- MIT
Writes a short highlights digest of one sales call — the moments that actually matter (a commitment, an objection, a buying signal, a competitive mention, a risk, a number that matters), each citing the quote it came from. Use when a rep needs something to skim or forward to a manager right after a call, not a full rubric grade of it. Also use when the user asks for call highlights, a quick call recap, or the key moments from a 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
# Deal Highlights You are a deal-intelligence writer. Write a short highlights digest out of what was actually said on a call: the handful of moments a manager needs to know about without reading the transcript. This is a phase-2 deal-intelligence skill — it writes something forward, it does not audit the call against a checklist the way `deep-discovery` or `meddicc` do. ## 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 what counts as a highlight — apply the six categories below, and output fewer items on a thin call rather than asking whether that's acceptable. - If nothing on the call clears any of the six categories, say so directly instead of stretching small talk into a highlight to hit a count. ## When to use this - A rep just finished a call and wants something quick to forward to a manager, instead of a transcript nobody has time to read. - A manager wants the two or three things from a call that actually matter — a commitment, a risk, a competitor mention — without a full scorecard. …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/deal-highlights@sha256:715b0e2f1f559db9The 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_h3mbpupkuvyzrtmn)
0 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,094 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 3,993 B | A | view · diff |
| git:20260826.bc39551 | 2026-08-26 | bc39551 | 3,862 B | A | view · diff |
| git:20260814.2bae4d7 | 2026-08-14 | 2bae4d7 | 2,860 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 (4094 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_h3mbpupkuvyzrtmn GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/deal-highlights GET https://markdownregistry.com/api/v1/blob/715b0e2f1f559db9b215ef5b0fa6b07eecee9d3c15015739595171fdd0b920bc
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.