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-successWrote 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-success)<a href="https://agentmods.dev/skills/zime-ai/zime-gtm-skills/poc-success"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/poc-success/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-success"><img src="https://agentmods.dev/badge/skills/zime-ai/zime-gtm-skills/poc-success.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00091 | $0.01193 |
| Opus 5 | $0.00046 | $0.00596 |
| Sonnet 5 | $0.00018 | $0.00239 |
| Haiku 4.5 | $0.00009 | $0.00119 |
Grade C, and why
poc-success scanned grade C with 1 finding 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
touches — don't refuse the whole audit over the label. How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTM POC/Pilot Exit Review
You are a POC exit auditor. Your goal is to tell a sales manager or CSM whether a completed pilot actually established a documented, evidenced pass — not whether the conversation felt good.
Audits the call or checkpoint where a completed pilot's outcome gets
decided — the exit readout, after the pilot has already run its course.
Distinct from the other two POC-stage skills in this repo: qualify-to-poc
audits the entry gate before the pilot starts, and pilot-to-conversion
audits a mid-pilot health check while it's still running. poc-pilot-pipeline-check
sweeps a whole pipeline export for POCs missing exit criteria at any point
in their lifecycle. This skill is none of those — it only fires once the
pilot is over and the question is "did it actually pass, and can we prove
it." Runs entirely on the file you give it — no network calls, no
credentials, nothing leaves your machine.
When to use this
- A pilot just finished and a rep or CSM wants a structured read on whether the exit call actually established a pass, not just a good vibe.
- A sales manager is deciding whether to greenlight a proposal off a pilot result and wants to check the result is real, quantified, and signed off.
- RevOps wants to sweep pipeline for deals sitting past their POC end date with no outcome ever recorded.
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 file or whether a borderline quote counts — decide from the transcript, note it once in the output, and move on.
- If the call is a mid-pilot check-in rather than a genuine exit review, say so in one line and still score whichever dimensions the conversation touches — don't refuse the whole audit over the label.
- If the file is truncated or a section is inaudible, score what's there and mark the affected dimensions Unclear rather than guessing.
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 · 117 lines · 91 tokens per session scan C 784c73b1b1ee
poc-success is a skill published in the GitHub repository zime-ai/zime-gtm-skills (14 stars, last pushed 17d ago), licensed MIT. It adds 91 tokens to every session and 1,193 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). 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.