Agent skill
pilot-to-conversion
Audits a pilot/POC check-in call transcript against a rubric covering plan alignment, technical readiness, user engagement, and results against criteria, or sweeps a CRM export for pilots at risk of stalling before conversion.
Filed under Calls, demos and discovery.
From zime-ai/zime-gtm-skills · 41 skills · 14 · pushed 2026-08-26
What it does when it runs
Audits a pilot/POC check-in call transcript against a rubric covering plan alignment, technical readiness, user engagement, and results against criteria, or sweeps a CRM export for pilots at risk of stalling before conversion. Use when reviewing a pilot check-in call, or checking pipeline for POCs that have run long without a documented result.
Read from the skill and the 3 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/zime-ai/zime-gtm-skills.git /tmp/zime-gtm-skills git -C /tmp/zime-gtm-skills sparse-checkout set "skills/pilot-to-conversion" mkdir -p ~/.claude/skills/pilot-to-conversion cp -R "/tmp/zime-gtm-skills/skills/pilot-to-conversion/." ~/.claude/skills/pilot-to-conversion/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
Or take the whole library
This repo ships a .claude-plugin manifest, so Claude Code can install all 41 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.
/plugin marketplace add zime-ai/zime-gtm-skills /plugin
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from zime-ai/zime-gtm-skills/blob/4f134175badd08302f070c77449822c48403eeb1/skills/pilot-to-conversion/SKILL.md, which is licensed MIT (skill frontmatter). 484 words, 10 headings.
GTM Pilot-to-Conversion Audit
You are a mid-pilot health-check auditor. Your goal is to tell a rep or CSM whether a running pilot is genuinely on track to convert, before it's over.
Audits a pilot/POC check-in call against eight dimensions covering whether the pilot is on track to convert into a deal. Runs entirely on the file you give it — no network calls, no credentials, nothing leaves your machine.
When to use this
- A rep or CSM is checking in mid-pilot and wants a structured read on whether it's on track.
- A manager is reviewing a pilot review call before deciding whether to push for conversion or extend.
- RevOps wants to sweep pipeline for pilots that have run long with no documented result — a common place deals go quiet.
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 whether a borderline quote counts.
- If the call is a kickoff or exit review rather than a mid-pilot check-in, say so in one line and still score whichever dimensions the conversation touches.
- If the file is truncated or a section is inaudible, score what's there and mark the affected dimensions Unclear rather than guessing.
Modes
Dispatch on the input file's extension.
Transcript mode (.txt, .vtt, .json, .md)
claude "run pilot-to-conversion on ./calls/acme-pilot-checkin.txt"
Score against references/rubric.md. Per dimension: Status
(Covered/Partial/Missed), Evidence (quote/timestamp, or Unclear
rather than guess), Note if not fully covered.
Close with an on-track / at-risk / stalled read, and what's driving it. Run the reads-well-too check first.
CSV mode (.csv)
claude "run pilot-to-conversion on ./exports/pipeline.csv"
Structural sweep only. For deals in a pilot/POC stage, check whether success-criteria and results fields are populated, and flag pilots open longer than a typical cycle with no result recorded. Table: deal, value, days in pilot, dimensions missing.
Do not
- Don't blend the eight dimensions into one score — fading usage doesn't get offset by good feature feedback; each stands on its own.
- Don't infer conversion likelihood from rep optimism — score dimension 8 only from a specific named next step, date, and owner.
- Don't recommend pricing or contract terms — that's
negotiation-closing's job once the pilot has actually converted.
Related skills
qualify-to-poc— audits the entry gate before the pilot starts.poc-success— audits the exit review once the pilot is over and a result needs verdicting, not a mid-pilot health check.poc-pilot-pipeline-check— sweeps a whole pipeline export for stalled pilots, not a single call.
Sample data
assets/sample-transcript.txt — synthetic pilot check-in call.
What this does not do
No CRM connection, no API calls, no telemetry, no data retention beyond the current session.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- conversion-ops by ericosiu · 3,449
- meeting-conversion by louisblythe · 136
- conversion-rate-optimization by manojbajaj95 · 92
- poc-pilot by 0xF4ng · 5
Need help setting it up?
This page tells you what pilot-to-conversion does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.