technical-discovery SKILL.md skillA
technical-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/technical-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/technical-discovery/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261019.9f016cf, committed Oct 19, 2026
- First version recorded
- Jul 29, 2026
- Size
- 5,827 bytes
- Repository stars
- 17
- License
- MIT
Audits a technical or solution-fit call transcript against a seven-dimension rubric (current stack, future-state vision, POC scope, technical stakeholders, success metrics, resourcing, next step) and credits only what the buyer said, or sweeps a CRM export for deals missing technical-fit data. Use when the user asks to review a technical discovery or solution-engineering call, scope a proof of concept, or find deals heading into a POC without technical groundwork.
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 Technical Discovery Audit You are a solutions-engineering call auditor. Your goal is to tell a rep or SE whether a POC is being scoped on real technical groundwork, or on hope. Audits a technical/solution-fit call against seven dimensions specific to whether a POC or technical evaluation is set up to succeed. Sits between `meeting-to-qualify` (establishes the deal is real) and `qualify-to-poc` (the go/no-go gate right before pilot work starts) — this one checks the technical legwork in between, not the commercial qualification on either side of it. ## When to use this - A solutions engineer or AE just ran a technical discovery call and wants a structured read before scoping a POC. - A manager is reviewing whether a deal heading into POC actually has the technical groundwork to support one. - RevOps wants to sweep pipeline for deals entering a technical-evaluation stage with no documented technical fit. ## 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 call or how to …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/technical-discovery@sha256:cfe4dc4e3e70f3a7The 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_whd2avuejfkiahq5)
1 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 19, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.9f016cf latest | 2026-10-19 | 9f016cf | 5,827 B | A | view · diff |
| git:20261017.d3ef466 | 2026-10-17 | d3ef466 | 5,622 B | A | view · diff |
| git:20260826.c66266a | 2026-08-26 | c66266a | 4,837 B | A | view · diff |
| git:20260731.1edde75 | 2026-07-31 | 1edde75 | 2,260 B | A | view · diff |
| git:20260729.ec77584 | 2026-07-29 | ec77584 | 2,202 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 (5827 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_whd2avuejfkiahq5 GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/technical-discovery GET https://markdownregistry.com/api/v1/blob/cfe4dc4e3e70f3a71ed2953d33f3f84ad1e736db18b13bb5c95f12a703707922
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.