Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add swan-gtm/gtm-skills --skill discovery-to-demo-bridgegit clone --depth 1 https://github.com/swan-gtm/gtm-skillsWrote 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/swan-gtm/gtm-skills/discovery-to-demo-bridge)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/discovery-to-demo-bridge"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/discovery-to-demo-bridge/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/swan-gtm/gtm-skills/discovery-to-demo-bridge"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/discovery-to-demo-bridge.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.00160 | $0.01943 |
| Opus 5 | $0.00080 | $0.00971 |
| Sonnet 5 | $0.00032 | $0.00389 |
| Haiku 4.5 | $0.00016 | $0.00194 |
Grade A, and why
discovery-to-demo-bridge 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 9d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose & When to Use
Most demos fail the same way: the rep shows everything the product does and hopes something sticks. The buyer leaves with indigestion — a blur of features, no clear line back to a problem they care about. A good demo is the opposite. It is a short, sharp proof that a specific, quantified pain has a specific fix. Every screen shown answers the question the buyer is actually asking: "will this solve my problem, and is it worth the money?"
This skill bridges discovery and demo. It takes what you learned on the discovery call and turns it into a "Why This Demo" plan: for each pain worth showing, it quantifies the cost of the pain, names the root cause, and maps the exact demo moment that proves the fix. Everything that doesn't earn a place goes on a cut-list.
Run this skill when any of these are true:
- You have discovery notes and a demo is the next step.
- Discovery surfaced multiple pains and you must decide what to show — and what to skip.
- A prior demo went long, went wide, and didn't move the deal.
- The buyer (or your manager) is asking "what are we going to cover and why."
- You catch yourself planning a feature tour instead of a proof.
Do not run this if discovery is not actually done — if you cannot name a single quantified pain, the answer is another discovery conversation, not a demo. A "Why This Demo" plan built on vague pain is just a feature tour with a title.
Procedure
Inputs you need
Collect these before building the plan. Where a number or fact is missing, do not
invent it — mark it [CONFIRM WITH BUYER] and make confirming it part of the pre-demo
follow-up.
- Deal context: company, champion (name + role), deal stage, who will attend the demo.
- Pains stated in discovery — in the buyer's own words, ideally direct quotes or close paraphrases from the call.
- Metrics and baselines tied to each pain — volume, time spent, headcount, deal sizes, cycle length, conversion, churn, cost — whatever lets you size the pain.
- The buyer's desired outcome and what "solved" looks like to them.
- Who is in the room for the demo and what each attendee cares about.
- The product moments you could show that map to these pains (your own knowledge of what proves what).
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.
- 9d ago First seen · 161 lines · 160 tokens per session scan A 4337da44aa3c
discovery-to-demo-bridge is a skill published in the GitHub repository swan-gtm/gtm-skills (150 stars, last pushed 2d ago), licensed MIT. It adds 160 tokens to every session and 1,943 once invoked, about $0.0008 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-09-03.
Other skills, from other repositories
fs-electric-studio
OpenDesign as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.
huashu-bento-insight
OpenDesign vs closed cloud design tools: a side-by-side displacement case on control, cost (BYOK), and lock-in. Built as a decision-grade B2B sales deck for evaluation committee.
html-ppt-product-launch
OpenDesign Teams: a launch-and-adoption proposal for a mid-market design team weighing a switch from closed cloud tools. Built as a decision-grade B2B sales deck for design team lead, IT.
geo-proposal
Auto-generate a professional, client-ready GEO service proposal from audit data. Creates a full proposal in markdown and PDF including executive summary, findings, recommended service packages (Basic/Standard/Premium), pricing, timeline, and terms. Use when user says "proposal", "proposta", "offerta", "preventivo"…
afrexai-lead-hunter
Enterprise-grade B2B lead generation, enrichment, scoring, and outreach sequencing for AI agents. Find ideal prospects, enrich with verified data, score against your ICP, and generate personalized outreach — all autonomously.
deliverability-monitoring
Monitor outbound deliverability health across domains, inboxes, DNS, bounces, spam placement, reply rates, and reputation signals. Produces alert thresholds, dashboard spec, weekly QA checklist, and remediation playbook. Use when inboxing drops, bounce rates rise, campaigns underperform, or new infrastructure launches.