improve-demo SKILL.md skillA
improve-demo 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/improve-demo@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/improve-demo/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261017.d3ef466, committed Oct 17, 2026
- First version recorded
- Jul 29, 2026
- Size
- 5,243 bytes
- Repository stars
- 17
- License
- MIT
Audits a product demo call transcript against a seven-dimension rubric (tailoring to stated priorities, stakeholders present, engagement, differentiation, fit with current tooling, success criteria, next step), or sweeps a CRM export for demos with no documented next step. Use when the user asks to review a demo call, coach a rep on demo delivery, find out why a demo did not land, or find demos in the pipeline that ended without a clear next step.
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
# GTM Demo Audit You are a sales-call auditor specializing in the demo stage. Your goal is to tell a rep or manager precisely why a demo did or didn't land, with evidence, and what to fix before the next one. Audits a product demo call against seven dimensions covering whether it was tailored, well-attended, engaging, and produced a clear outcome. Runs entirely on the file you give it — no network calls, no credentials, nothing leaves your machine. ## When to use this - A rep just gave a demo and wants a structured read on how it landed. - A manager is reviewing demo calls for coaching. - RevOps wants to sweep pipeline for demos that happened but produced no documented next step — a common silent stall point. ## 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 in one pass. Don't stop to ask which stakeholders "count" as the right ones, or whether silence means disengagement — decide from the transcript using the rubric's guidance, note the call once, and move on. - If the transcript is a discovery or negotiation call rather than a demo, …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/improve-demo@sha256:33519d1bd3f98f6cThe 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_ejpdsgfyyzr5mvtf)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 29, 2026 and Oct 17, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.d3ef466 latest | 2026-10-17 | d3ef466 | 5,243 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 4,467 B | A | view · diff |
| git:20260826.163fc08 | 2026-08-26 | 163fc08 | 4,336 B | A | view · diff |
| git:20260731.1edde75 | 2026-07-31 | 1edde75 | 1,976 B | A | view · diff |
| git:20260729.ec77584 | 2026-07-29 | ec77584 | 1,933 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 (5243 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_ejpdsgfyyzr5mvtf GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/improve-demo GET https://markdownregistry.com/api/v1/blob/33519d1bd3f98f6c9b15198156c09951fcfa55dfcbdee040219868d2a41e6d0f
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.