Skip to content
Back to search

splitdemo

MarketplaceWorks with Claude CodeGitHub

splitdemo skills for Claude Code.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/ramonvdo--splitdemo/badge.svg)](/listings/ramonvdo--splitdemo)

HTML

<a href="/listings/ramonvdo--splitdemo"><img src="/api/listings/ramonvdo--splitdemo/badge.svg" alt="findsafeskills safety rating" /></a>

Install

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 19 lines
  1. {
  2. "$schema": "https://json.schemastore.org/claude-code-marketplace-manifest.json",
  3. "name": "splitdemo",
  4. "description": "splitdemo skills for Claude Code.",
  5. "owner": {
  6. "name": "Ramon",
  7. "url": "https://github.com/Ramonvdo"
  8. },
  9. "plugins": [
  10. {
  11. "name": "splitdemo",
  12. "source": "./",
  13. "description": "Turn a job post or a process description into a demo a non-technical owner can watch: one scripted story told step by step, or across up to four app-like panels at once, ending on a results slide that asks the viewer's own numbers and shows the ROI on them. Share it as a link or film it.",
  14. "version": "0.3.0",
  15. "license": "MIT",
  16. "keywords": ["splitdemo", "demo", "automation", "agency", "sales", "proposal", "video"]
  17. }
  18. ]
  19. }
README.md · README · 136 lines
  1. # splitdemo
  2. Demos of automation and AI systems that a business owner can follow. One scripted story plays step by step: a line of text says what is about to happen, then the screen it happens on shows it at full size. The story ends on a results slide that asks the owner a few of their own numbers and shows what the system is worth on them. The same story also plays as a split screen, on up to four app-like screens at once.
  3. ![A new patient texts a dental practice after closing time. The system reads the message, answers with open times, puts the patient on the list and books the visit, across four screens at once.](docs/speed-to-lead.gif)
  4. The picture shows fast mode, the split screen. A link opens in explainer mode, which tells the same story one screen at a time.
  5. ## Why
  6. Most automation demos show the workflow canvas. The person paying for the system does not read canvases. They want to know what their customer sees, where the lead ends up, and what changed in their numbers.
  7. splitdemo tells that as a story in steps. The first card says what is at stake: "A $180 new patient sends this text. Your practice closed at six." The text goes out on the patient's phone. One card and one diagram show what the system does while nobody is at the desk. The screens after that show what came of it: the reply on the phone, the patient on your list, the reply time going from 14 hours to 38 seconds. One screen changes at a time, so there is time to read it.
  8. Fast mode puts the customer's phone, the automation, the CRM and the week's numbers next to each other on one wall, and the same story moves through all of them at once. It is the short version, for a viewer who already knows the story.
  9. ## What is in the box
  10. - A demo is one JSON file: the panels, a story in steps, the outcome and the numbers for the calculator. There is no code per demo, so swapping the CRM for a spreadsheet means changing one `type`.
  11. - That one file plays two ways. Explainer shows a card and then one screen at a time, and takes 60 to 100 seconds. Fast shows the whole wall and takes 30 to 50. The switch top left goes between them and keeps the step.
  12. - A results slide closes the story. It shows the outcome numbers next to what they were, then asks the owner up to four of their own numbers, one question a screen. The report works out what the system adds a month and over the first year, and draws it: twelve months against carrying on as today, and a funnel where the business has a pipeline, so the stage that widens shows.
  13. - Nine panels come with it: phone, form, inbox, workflow, CRM board, sheet, calendar, email campaign and a numbers board with a chart. Each looks like the kind of app it stands for, with its own colours and typeface: the sheet has column letters and a formula bar, the CRM has a board with deal cards. A panel takes the tool's name as a label, like "CRM in ClickUp", and carries no logo.
  14. - You can show a demo live on a call from your own machine, send it as a private link, or film it (the story or the wall, 1920x1080, upright for a phone, or a gif).
  15. - The Claude Code skills write a demo from a job post, a process description or a call transcript. They check it and look at every card and every screen before they hand it over.
  16. - Two checks catch a bad demo before a prospect does. One finds an action that cannot happen or a caption that is too long, prints how long each mode plays, and notes a step that asks too much of the viewer. The other finds text that gets cut off or ends in three dots, in both modes, on a laptop or a phone.
  17. Every demo carries a small "Scripted example" tag. Nothing connects to a real system; it is a simulation of what the system will do.
  18. ## Start with Claude Code
  19. ```
  20. /plugin install splitdemo --marketplace Ramonvdo/splitdemo
  21. /splitdemo-onboarding
  22. /splitdemo <paste a job post, or describe the problem>
  23. ```
  24. Onboarding runs once. It installs the app, asks where your demos should live and whether you want links (Cloudflare) or local demos only, and writes `~/.splitdemo/config.json`.
  25. After that:
  26. | Command | What it does |
  27. | --- | --- |
  28. | `/splitdemo <job post or problem>` | Writes the story, picks the panels, builds the demo, checks it and opens it. |
  29. | `/splitdemo <slug> <change>` | Changes a demo you already have. |
  30. | `/splitdemo-share <slug>` | Publishes it under a link nobody can guess, after showing you what goes online. |
  31. | `/splitdemo-video <slug>` | Films it as an mp4: the story step by step, or the wall with `--fast`. `--portrait` is for a phone and `--gif` for a README or an email. |
  32. | `/splitdemo panel <what it shows>` | Adds a panel type for a screen the nine cannot show. |
  33. ## Start by hand
  34. Needs Node 22.18 or newer.
  35. ```bash
  36. git clone https://github.com/Ramonvdo/splitdemo
  37. cd splitdemo
  38. npm ci
  39. npm run dev
  40. ```
  41. Open http://localhost:4310 for the three examples. They open in explainer mode; `?mode=fast` at the end of an address opens the wall. http://localhost:4310/__panels shows every panel on its own.
  42. On a call: the switch top left goes between Explainer and Fast. Space plays and pauses, the arrow keys step through the story, `R` plays it again and `H` hides the bars. In fast mode `1` to `4` enlarge a panel. On the results slide you type the prospect's own numbers into the fields.
  43. ## What a demo looks like
  44. ```json
  45. {
  46. "v": 1,
  47. "title": "A new patient texts after closing time",
  48. "panels": [
  49. { "id": "phone", "type": "phone", "label": "Patient's phone", "config": { "contact": "Harbor Dental" } },
  50. { "id": "crm", "type": "crm", "label": "Your patient list", "config": { "columns": [{ "id": "new", "title": "New" }, { "id": "booked", "title": "Booked" }] } }
  51. ],
  52. "beats": [
  53. {
  54. "say": "A $180 new patient sends this text. Your practice closed at six.",
  55. "do": [{ "on": "phone", "type": "send", "text": "Hi, I chipped a tooth. Can I come in this week?" }]
  56. },
  57. {
  58. "say": "Dana is on your patient list before you have seen her text.",
  59. "do": [{ "on": "crm", "type": "add", "id": "dana", "to": "new", "title": "Dana Whitfield" }]
  60. }
  61. ],
  62. "outcome": [{ "value": "38 sec", "label": "to first reply", "was": "14 h" }],
  63. "results": {
  64. "title": "What a missed message costs",
  65. "roi": {
  66. "currency": "USD",
  67. "inputs": [
  68. { "id": "texts", "label": "After-hours texts a month", "ask": "How many texts come in after closing, in a month?", "value": 40 },
  69. { "id": "booked", "label": "Share of those that book a visit", "ask": "Of every 100 of those texts, how many book a visit today?", "value": 10, "kind": "percent" },
  70. { "id": "visit", "label": "Worth of a first visit", "ask": "What is a first visit worth to you?", "value": 180, "kind": "money" }
  71. ],
  72. "lever": { "input": "booked", "add": 20 }
  73. }
  74. }
  75. }
  76. ```
  77. Each beat is one step: a caption and the actions it brings. In explainer mode the caption is the card, and the actions show one screen at a time in the order they are written. In fast mode they play on the wall while the caption stands under it. Timing follows from the text, so you write no numbers unless you want a pause on the wall. A demo plays by itself. When you present one live, a beat with `"wait": "click"` holds until the viewer presses the button themselves.
  78. `results` is optional. The calculator is one chain of numbers that multiply, and a lever: the one number in the chain the system changes. Here 40 texts × 10% booked × $180 is $720 a month today. With 20 points more booked it is $2,160, so the slide starts at $1,440 extra a month. An input with an `ask` is a question the slide puts to the viewer. The rest are your estimates, and the viewer can change every number in the report.
  79. The full examples are in [`examples/`](examples). The list of panels with their actions is [`src/panels/INDEX.md`](src/panels/INDEX.md), and each panel's folder says how to use it well.
  80. Your own demos live outside this repo, in a workspace folder you choose: `<workspace>/demos/<slug>/demo.json`. That keeps prospect data out of a clone you might push.
  81. ## Commands
  82. | Command | What it does |
  83. | --- | --- |
  84. | `npm run dev` | Plays every demo at `http://localhost:4310/<slug>/` and reloads when its file changes. |
  85. | `npm run check -- <slug>` | Says whether the demo can play, where in the file it goes wrong, and how long each mode plays. |
  86. | `npm run shots -- <slug>` | A picture of every card, screen and beat in both modes, and a failure when any text is cut off or shortened. `--mode explainer` or `--mode fast` shoots one. |
  87. | `npm run share -- <slug>` | Publishes the demo to your Cloudflare Worker. `--dry-run` publishes nothing. |
  88. | `npm run export -- <slug>` | Writes the demo as one plain folder for any static host. |
  89. | `npm run record -- <slug>` | Films the story. `--fast` films the wall, `--portrait` and `--gif` as above. Needs ffmpeg. |
  90. | `npm test`, `npm run e2e` | Unit tests, and the browser tests. |
  91. ## Sharing
  92. A shared demo gets its own folder under a name like `harbor-dental-x7k2m9qp`. There is no index page, a wrong address returns a real 404, and the pages ask search engines to stay out. One prospect's folder holds nothing of another's.
  93. Every link has an end date. A demo is shared for 30 days unless you say otherwise, and it drops out at the next publish after that. `npm run share -- --stop <slug>` takes one offline sooner.
  94. A link opens in explainer mode. The same link with `?mode=fast` at the end opens the wall. With `?q=report` the results slide opens on the report with your example numbers, and offers the questions from there.
  95. By default a share shows you what will go online and waits for a yes. Set `"share": "auto"` in the settings to skip the question.
  96. ## Adding a panel
  97. A panel is one folder in `src/panels/` with seven files: a schema, a pure reducer with its tests, a view with its skin, a short guide for the agent and a working example. The app picks it up by name. [`CONTRIBUTING.md`](CONTRIBUTING.md) has the contract.
  98. ## License
  99. MIT. The chart components come from [Bklit UI](https://github.com/bklit/bklit-ui), also MIT. See [`THIRD_PARTY_NOTICES.md`](THIRD_PARTY_NOTICES.md).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.