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/poc-pilot-pipeline-checkWrote 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/poc-pilot-pipeline-check)<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/poc-pilot-pipeline-check"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/poc-pilot-pipeline-check/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/poc-pilot-pipeline-check"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/poc-pilot-pipeline-check.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.00064 | $0.01104 |
| Opus 5 | $0.00032 | $0.00552 |
| Sonnet 5 | $0.00013 | $0.00221 |
| Haiku 4.5 | $0.00006 | $0.00110 |
Grade A, and why
poc-pilot-pipeline-check 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
POC/Pilot Pipeline Check
You are a pipeline-hygiene auditor. Sweep every deal sitting in a POC or
pilot stage and flag which of them can never convert because nobody wrote
down what winning looks like. This is a pipeline-wide structural sweep
across every live POC at once, not a single-call audit — pilot-to-conversion
audits the individual check-in conversation that converts one pilot; use
this skill instead when the question is "which of our open POCs are already
dead and don't know it yet."
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. - Default to running end to end without stopping to ask which stage labels to match or how to handle a missing column — apply the defaults below, decide, and note the assumption once.
- If the in-scope filter returns zero rows (no POC/pilot-stage deals in the export), say so plainly and stop — don't force a check onto rows that don't exist.
When to use this
- RevOps wants a pipeline-wide read on POC/pilot health before a forecast call.
- A manager is triaging a rep's pipeline and wants to know which POCs have no defined exit before spending more time on them.
- Nobody has looked at the POC/pilot stage in a while and deals may be sitting there open-ended.
Input
A .csv deal/pipeline export. There is no transcript mode — this skill
only reads structured pipeline data, never a call.
Connector mode is optional and secondary: if a tool in the conversation can list opportunities/deals directly, use it and treat the returned rows exactly like CSV rows. Otherwise, work from the CSV file.
How to run it
claude "run poc-pilot-pipeline-check on ./exports/pipeline.csv"
- Detect columns. Match headers case-insensitively, ignoring
_/-/space differences. Accepted synonyms are listed inreferences/rubric.md. If a column a check needs is absent, that check reports Unknown (column missing) once, up front — never infer a missing column's value from another column. - Filter to stage. Keep rows whose stage fuzzy-matches POC/pilot (e.g.
POC,Pilot,POC/Pilot,Proof of Concept). Report how many rows were in scope out of the export's total. - Run every check in
references/rubric.mdagainst each in-scope row. Each check returns Flagged, Clean, or Unknown. - Cite evidence. Every flagged deal cites the column name and the
actual cell value that triggered the flag, e.g.
champion = (empty)orpoc_end_date = 2026-01-14. A flag with no cited cell does not ship. - Reads-well-too check. Confirm the two genuinely healthy deals in
assets/sample-pipeline-poc-pilot-pipeline-check.csvcome back Clean. A rubric that flags everything is useless.
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 · 114 lines · 64 tokens per session scan A e262fa76a063
poc-pilot-pipeline-check is a skill published in the GitHub repository zime-ai/zime-gtm-skills (14 stars, last pushed 17d ago), licensed MIT. It adds 64 tokens to every session and 1,104 once invoked, about $0.0003 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.
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.
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.
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.
demo-storyline
Create a buyer-centered B2B SaaS demo storyline that maps product moments to buyer pain, uses realistic data, prompts discovery throughout, and ends with a clear recap and next step.