Skip to main content
skill CX Codex

demo-builder — Claude Code skill: demos and installation

The demo-builder Claude Code skill turns a short spec into an interactive product demo. It activates for requests to mock up a product or show how a workflow could work.

MIT ★ 92 updated 2026-11-06

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add Jakeschincariol/whale-skill
/plugin install whale-skill@whale-skill
Open on GitHub

What demo-builder does

The skill validates a spec and generates a single HTML page with sample records, an action button, changing row statuses, and a running total. A banner marks the page as a demo using sample data. It runs without a server or network calls.

Save the spec as whale/demo.json, then run demo.py check followed by demo.py build. The commands need python3. Real customer records must stay out of the demo; sending or publishing the file requires the user's explicit approval. The HTML can be attached as a file or placed on a static host.

What it helps with

  • turn a short product spec into a clickable prototype
  • show records changing status after a button press
  • create a sample-data demo that runs without a server

Example prompts for the agent

  • Build a demo for tracking overdue invoices.
  • Check whale/demo.json and generate the HTML demo.
  • Make a clickable prototype with one action button and sample records.

How to install demo-builder

1Plugin marketplace

/plugin marketplace add Jakeschincariol/whale-skill
/plugin install whale-skill@whale-skill

This installs the whole whale-skill plugin with all its skills

2Skills CLI (Vercel)

npx skills add Jakeschincariol/whale-skill --skill demo-builder -a claude-code

3Manually: put the files in place

~/.claude/skills/demo-builder/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/demo-builder/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about demo-builder

How do I install demo-builder in Claude Code?

Run these commands in order: /plugin marketplace add Jakeschincariol/whale-skill, then /plugin install whale-skill@whale-skill.

What does demo-builder do?

It turns a compact spec into an HTML demo with sample records, an action button, and changing statuses. A banner identifies it as a demo rather than a shipped product.

What does demo-builder need to run?

The build commands require python3. The skill creates an HTML file without a server or network calls.

Source text

SKILL.md · MIT
---
name: demo-builder
description: >-
  Demo Builder. Builds a demo showing how your product solves the problem, before the product exists.
  Turns a small spec into one self-contained HTML page that runs anywhere with no server: sample
  records, one button, every row moving through its statuses and a total counting up, with a banner
  that always says it is a demo with sample data. Claude can then make it look and behave more like
  the real thing for this buyer. Use when the user says "build a demo", "mock this up", "show how it
  would work", "I need something to show them", "prototype", or "make a clickable demo".
argument-hint: "[check <spec> | build <spec>]"
---

# demo-builder

Nobody buys a description. A demo that takes 2 minutes to watch does what a 20-page deck can't: it lets
someone see their problem go away. It only has to show the one moment that matters, and it has to be
honest about what it is.

`${CLAUDE_SKILL_DIR}` below is this skill's folder (where this SKILL.md lives).

```bash
python3 "${CLAUDE_SKILL_DIR}/demo.py" check --spec "${CLAUDE_SKILL_DIR}/demo.example.json"
python3 "${CLAUDE_SKILL_DIR}/demo.py" build --spec "${CLAUDE_SKILL_DIR}/demo.example.json" --out whale/demo/index.html
```

## The spec

```
title        your product's name
subtitle     the one job it does here ("Late invoices")
button       the one action ("Chase all")
total_label  what the number at the bottom means ("Collected")
sample_data  must be true: a demo never shows a real customer's records
statuses     what each row moves through, in order (["Reminder sent", "Paid"])
rows         3 to 12: name, amount ($1,234.00), note ("71 days late")
accent       optional color, like #D97757
```

## Steps

1. **Find the moment.** Ask: what is the one screen where the problem goes away? For late invoices, it is a list
   of overdue invoices, one button, and the money coming in. Everything else can wait.
2. **Write the spec.** Save it as `whale/demo.json`. Use sample names and round, believable numbers from the
   buyer's world. Never use a real customer's data, and never the buyer's own records without their written okay.
3. **Build it.** `demo.py check`, then `demo.py build`. It writes one HTML file with no network calls.
4. **Open it and press the button yourself.** Then show the user. Watch for anything that looks more finished than
   it is, and say so.
5. **Make it theirs, if it helps.** Claude can restyle the page for one buyer or add a second screen. Keep the banner.
   Keep it small: a demo that takes a week to build has stopped saving time.
6. **Host it.** Any static host works (GitHub Pages, Netlify, Cloudflare Pages), or attach the file. Publishing it is
   the user's call. `/whale-hunter` puts the link in the pitch.

## Showing it

- Say first: "This is a demo with sample data. Here's how it will work for you."
- Under 2 minutes. Show the problem, press the button, show the result, stop.
- Then ask, and listen: "How close is this to how you'd want it to work?" Every answer is a requirement.

## Example from the reel

"Build a demo that chases late invoices for a freight company." Your Product, Late invoices, five rows from Granite
State Tile ($15,300.00, 71 days late) to Tern Bay Seafood ($5,240.00, 33 days late). "Chase all" moves each row to
Reminder sent, then Paid, and the total counts up to $48,210.00. This is `demo.example.json` (illustrative: every
business and amount in it is fictional).

## What it never does

- Never removes the banner. A demo that passes for a shipped product is a false promise, and it comes back as a refund.
- Never puts a real customer's records in a demo.
- Never promises a feature in a demo that the user doesn't intend to build.

## Consent and truth

- Nothing is sent, published or charged without the user's explicit yes. This skill only writes a file.
- A demo shows how it will work, not what already exists. Say so every time you show it.
- Never invent a result, a client or a review. The numbers in a demo are sample data and are labelled that way.

© Jake Schincariol · MIT · Jakeschincariol/whale-skill

Similar skills

SKILL.md skills catalog →

From the same set12

The whole set →
pricing This Claude Code skill calculates a price from what a customer already spends on the problem. Ask for pricing options, a check of a proposed amount, or a price saved to a deal. CX Codex +1 ★ 92repo stars offer-builder The offer-builder Claude Code skill drafts a one-page offer with its price, delivery date, and refund terms. It activates on requests to write an offer, prepare a proposal, or answer a prospect asking for details. CX Codex +1 ★ 92repo stars case-study A skill for Claude Code drafts a customer case study from real figures and the customer's own words. It runs when asked for a testimonial or customer story after delivery. CX Codex +1 ★ 92repo stars requirements The requirements Claude Code skill turns paying customers’ requests into a ranked feature list. It activates after a customer pays or when the conversation turns to scope, specs, or feature requests. CX Codex +1 ★ 92repo stars launch-planner The launch-planner Claude Code skill schedules a product launch after a customer pays. It works back from the promised delivery date and holds the public release until customer orders are fulfilled. CX Codex +1 ★ 92repo stars objection-handler The objection-handler Claude Code skill drafts replies to sales objections using the terms of your deal. It activates when someone pushes back, asks a question, or sends a message you’re unsure how to answer. CX Codex +1 ★ 92repo stars follow-up This Claude Code skill tracks follow-ups after a pitch or offer. It lists deals due for a message, drafts one, then waits for approval before sending. CX Codex +1 ★ 92repo stars market-researcher The market-researcher Claude Code skill finds business problems that already have a budget. It responds to requests for product ideas, market research, and idea validation. CX Codex +1 ★ 92repo stars

Project sponsors

Companies that keep this analytics open