persona-based-discovery SKILL.md skillA
persona-based-discovery 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/persona-based-discovery@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/persona-based-discovery/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261019.9f016cf, committed Oct 19, 2026
- First version recorded
- Aug 10, 2026
- Size
- 6,476 bytes
- Repository stars
- 17
- License
- MIT
Audits whether a discovery call's questions and framing were tailored to the specific buyer persona in the room (technical evaluator, economic buyer, end user, and so on), or sweeps a CRM export for deals with no persona or role data on contacts. Use when the user asks whether a rep adapted to who they were talking to, how well the pitch fit each persona, or which pipeline deals are missing contact-role fields.
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 Persona-Based Discovery Audit You are a sales-call auditor specializing in persona adaptation. Your goal is to tell a rep or manager whether the call actually read the room, or just ran the standard pitch regardless of who was on the line. Audits a discovery call against five dimensions of persona-adaptation: did the rep correctly identify who they were talking to and adjust pain framing, proof points, objection-handling, and next steps to that specific role — rather than running the same script regardless of who's on the call. This is narrower than `deep-discovery` (the generic, persona-agnostic 9-dimension discovery rubric) — use that one for overall discovery thoroughness, use this one specifically to check whether the rep read the room. ## When to use this - A rep had a discovery call with a named persona (a technical evaluator, an economic buyer, an end user) and a manager wants to know if the call was actually adapted to that person, or just the standard pitch. - A call had multiple stakeholders on it and you want to check whether the rep addressed each persona's concerns distinctly, or treated the room as one audience. …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/persona-based-discovery@sha256:7ef8831aade55c6bThe 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_nhas6cby7uxhbe4s)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 10, 2026 and Oct 19, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.9f016cf latest | 2026-10-19 | 9f016cf | 6,476 B | A | view · diff |
| git:20261017.d3ef466 | 2026-10-17 | d3ef466 | 6,271 B | A | view · diff |
| git:20260826.c66266a | 2026-08-26 | c66266a | 6,149 B | A | view · diff |
| git:20260810.8e1ce3c | 2026-08-10 | 8e1ce3c | 4,046 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 (6476 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_nhas6cby7uxhbe4s GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/persona-based-discovery GET https://markdownregistry.com/api/v1/blob/7ef8831aade55c6bdf6960228eb3bfe249f30b6ebcdc495bbebda9ecfd81b769
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.