Individual skill

discovery-to-demo-bridge

Use this skill in the gap between a discovery call and the demo that follows — when you have discovery notes and need to turn them into a demo that proves value instead of dumping features. Run it when a rep is about to "walk through the product," when discovery surfaced several pains and you need to decide what to actually show, when a previous demo fell flat or caused "indigestion" (too much shown, nothing landed), or when you need to justify to the buyer why this demo is worth their time. The agent quantifies each discovered pain in dollars/ARR/time, ties it to a root cause, and maps the exact demo moment that proves the fix — producing a "Why This Demo" plan and an explicit cut-list of features to skip.

skills/gal-aga/discovery-to-demo-bridge/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## 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.
Back to top