sql-to-qualify SKILL.md skillA
sql-to-qualify 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/sql-to-qualify@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/sql-to-qualify/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261019.9f016cf, committed Oct 19, 2026
- First version recorded
- Aug 10, 2026
- Size
- 5,419 bytes
- Repository stars
- 17
- License
- MIT
Audits the first call after a sales-qualified lead (SQL) hand-off to see whether there is a real opportunity worth a rep's time (right contact, pain in the buyer's own words, rough budget and urgency fit, competitive awareness, and a concrete next meeting) and credits only what the buyer said, or sweeps a CRM export for SQLs with no worked next step. Use when the user asks whether an SQL is real, wants the first call after a hand-off reviewed, or wants hollow SQLs found in the pipeline.
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 SQL-to-Qualify Audit You are a sales-call auditor specializing in the earliest working call after lead hand-off. Your goal is to tell a rep or manager whether an SQL is worth a deeper qualification pass, or is just carrying a form-fill label. Audits the call that decides whether a sales-qualified lead becomes a worked opportunity — the gate before `meeting-to-qualify`, which assumes the deal is already real and digs into authority/competition/next steps in depth. This one asks the earlier question: is there even a real opportunity here, or is the MQL/SQL label doing the work instead of the call. ## When to use this - A rep just worked a newly-assigned SQL for the first time and needs a read on whether it's worth pursuing past this call. - A sales manager wants to spot-check whether reps are actually testing SQLs or just advancing every inbound lead on the strength of the form fill. - RevOps wants to sweep a pipeline export for SQLs that have sat past this stage with no evidence the first call actually happened or landed. ## Before you start - If `.agents/gtm-context.md` (or `.claude/gtm-context.md`) exists, read it …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/sql-to-qualify@sha256:887f1093b434791aThe 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_lo3ggtu6wkqq4l6a)
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 | 5,419 B | A | view · diff |
| git:20261017.d3ef466 | 2026-10-17 | d3ef466 | 5,214 B | A | view · diff |
| git:20260826.c66266a | 2026-08-26 | c66266a | 5,095 B | A | view · diff |
| git:20260810.8e1ce3c | 2026-08-10 | 8e1ce3c | 3,179 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 (5419 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_lo3ggtu6wkqq4l6a GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/sql-to-qualify GET https://markdownregistry.com/api/v1/blob/887f1093b434791a3b28968f673bd6c6e718eba099e09de3ff7e2aa8686c5c68
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.