Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/zime-ai/zime-gtm-skillsnpx agentmods add skills/zime-ai/zime-gtm-skills/sql-to-qualifyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zime-ai/zime-gtm-skills/sql-to-qualify)<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/sql-to-qualify"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/sql-to-qualify/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/sql-to-qualify"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/sql-to-qualify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00098 | $0.01198 |
| Opus 5 | $0.00049 | $0.00599 |
| Sonnet 5 | $0.00020 | $0.00240 |
| Haiku 4.5 | $0.00010 | $0.00120 |
Grade A, and why
sql-to-qualify scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 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 an ambiguous moment — apply the default rule at the point it comes up, decide, and note the assumption once.
- If the input isn't a first SQL follow-up call, say so in one line and still score whichever dimensions the conversation touches.
Modes
Transcript mode (.txt, .vtt, .json, .md)
claude "run sql-to-qualify on ./calls/acme-sql.txt"
- Read the whole transcript before scoring anything — competitive context or a next-meeting date often lands in the last minute.
- Score the call against each dimension in
references/rubric.md. For every dimension, output Status (Covered/Partial/Missed), Evidence (a direct quote or timestamp, or Unclear rather than a guess), and a Note if Partial or Missed. - Run the rubric's reads-well-too check before finalizing.
- Write the output in the exact shape under
## Output format.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 124 lines · 98 tokens per session scan A a831430c3b93
sql-to-qualify is a skill published in the GitHub repository zime-ai/zime-gtm-skills (14 stars, last pushed 16d ago), licensed MIT. It adds 98 tokens to every session and 1,198 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
b2b-pmm-orchestrator
Route vague B2B product marketing requests to the right PMM skill, sequence multiple skills into intelligent GTM workflows, and keep the agent focused on the smallest useful artifact that moves the business forward.
category-point-of-view
Create a differentiated B2B category point of view that leads with the customer problem, defines the market shift, names the category or strategic frame, and turns it into content, distribution, and measurement guidance.
ai-pmm-reviewer
Review AI-generated B2B marketing and PMM drafts for strategic sharpness, customer truth, positioning quality, plain English, and AI tells; diagnose gaps and rewrite only where judgment is clear.
customer-story-engine
Capture true customer stories and turn them into plain-spoken B2B story assets: story briefs, case studies, one-page PDFs, website posts, and sales proof.
sales-narrative-deck
Create a sales-ready B2B narrative deck outline that starts with buyer pain, teaches the market, shows the solution, supports a demo, and gives reps a clear path to proof, pricing, competition, recap, and next steps.