record-demo
Skill826 starsChanged 12 days agoMITView on GitHub
Record an MP4 product demo of a Nakama flow in BrowserOS (browseros-neo MCP) on the user's dev app at http://localhost:3003. Use when the user says /record-demo, "make a demo video", "record a demo of X", or asks for an mp4 that shows a feature working end to end (for example connecting an MCP server from chat and using it).
- Sends data out
15 other projects use a version of this.
Adopted by
Most recently taken up by
- tandryukha/aidemotheir own version, first seen Nov 9, 2026
- jamdotdev/jam-plugintheir own version, first seen Nov 8, 2026
- jamdotdev/skillstheir own version, first seen Nov 8, 2026
- nightly-labs/openbottheir own version, first seen Nov 8, 2026
- flopperj/dotfiles-coretheir own version, first seen Nov 1, 2026
- arnavpisces/skillstheir own version, first seen Nov 1, 2026
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- nightly-labs/openbot★ 7.9ksame name
- apify/mcp-cli★ 1.1ksame name
- apify/mcpc★ 1.1ksame name
- slackapi/slack-cli★ 322same name
- mcpware/pagecast★ 43same name
- tandryukha/aidemo★ 32same name
- WatermelonBros/reado★ 31same name
- jamdotdev/jam-plugin★ 11same name
- jamdotdev/skills★ 11same name
- flopperj/dotfiles-core★ 3same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adhd-pr-descriptionSkill
- eli5Skill
- plan-reviewSkill
- releaseSkill
- verify-bsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 6 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Use the user's app on http://localhost:3003 and their BrowserOS sign-ins.
- Very specific: line 25
Do not start another server.
- Distinctive: line 27
Never type a password. If a sign-in page needs one, stop and ask the user to sign in in BrowserOS.
- Distinctive: line 30
Keep frames, plans and videos in the scratchpad.
- Distinctive: line 31
Before you report done, look at the frames.
- Distinctive: line 44
Check that the start state is clean.
- Very specific: line 47
Do a dry run of the menus with snapshot (mode interactive) to learn the button names.
- Very specific: line 156
Put page.goto before recLoop.
- Very specific: line 163
If unsent is more than 0, the frame server did not get those frames.
- Very specific: line 164
Read flushErr and frame-server.log, fix the cause, and record the part again.
- Distinctive: line 182
If a part is bad, record a fix part (for example a follow-up prompt), or leave the part out of the plan.
- Very specific: line 187
Write $REC/plan.json. List the parts in play order.
- Distinctive: line 221
Leave the demo tabs open for the user.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Record a demo video in BrowserOS
Drive the real app in BrowserOS, capture frames with CDP screenshots, and
join them into an H.264 MP4. BrowserOS has no screen recorder. ffmpeg
screen capture hangs when the app has no macOS Screen Recording permission,
so do not use it.
Reference run: Canva MCP demo. Chat → + → MCP servers → Add MCP server → Connect Canva → Canva consent → ask for a poster → poster in chat → open in Canva.
Rules
- Use the user's app on
http://localhost:3003and their BrowserOS sign-ins. Do not start another server. If 3003 gives 502, start the API withNAKAMA_PORT=4310 bun run dev:server. - Never type a password. If a sign-in page needs one, stop and ask the user to sign in in BrowserOS. A consent click ("Allow") is OK only when the user asked you to do the sign-in.
- Keep frames, plans and videos in the scratchpad. Never commit them.
- Before you report done, look at the frames. Do not claim what you did not see.
- Tell the user what the demo changed in their data (new MCP server, new chats, files in third-party accounts).
Steps
1. Agree the story
Get from the user: the start screen, each step, and the end screen. Write it as 4–8 short shots. If it is not clear, give 3 numbered options.
2. Check the start state
- Check that the start state is clean. Example: a "connect" demo needs the server not to exist yet (MCP server names are unique). Ask before you delete user data to make it clean.
- Do a dry run of the menus with
snapshot(modeinteractive) to learn the button names. Close dialogs after (Escape) so the take starts clean.
3. Start the frame server and the relay tab
REC=<scratchpad>/record-demo
mkdir -p "$REC"
nohup bun .agents/skills/record-demo/scripts/frame-server.mjs "$REC/frames" 4399 > "$REC/frame-server.log" 2>&1 &
curl -s http://127.0.0.1:4399/Then, in BrowserOS:
name_sessionwith a short task label.run:const relay = await browser.open("http://127.0.0.1:4399/"); return relay.id;The relay tab posts frames to the server from the same origin, so CORS and mixed-content rules do not block it.run:const p = await browser.open("http://localhost:3003/chat?new=1"); return p.id;
4. Record in parts
A run call stops at 30 s. Record each part in its own run, with at most
25 s of capture. Paste this snippet at the top of each run, and set
RELAY_ID and TARGET_ID:
const RELAY = browser.page(RELAY_ID);
const REC = { target: TARGET_ID, on: true, buf: [], n: 0 };
// On a failed POST the frames go back in the buffer for the next flush. It never throws.
// page.evaluate gives { value, changed, page, settled }. The HTTP status is in res.value.
async function flush() {
if (!REC.buf.length) return;
const items = REC.buf.splice(0);
try {
const res = await RELAY.evaluate((it) => fetch("/frames", { method: "POST", headers: { "x-frame-relay": "1" }, body: JSON.stringify(it) }).then((r) => r.status), items);
if (res.value !== 200) throw new Error("frame server status " + JSON.stringify(res));
} catch (e) {
REC.buf.unshift(...items);
REC.err = String(e);
}
}
async function recLoop(ms) {
const end = Date.now() + ms;
while (REC.on && Date.now() < end) {
try {
const shot = await browser.page(REC.target).cdp("Page.captureScreenshot", JSON.stringify({ format: "jpeg", quality: 72 }));
REC.buf.push({ t: Date.now(), d: shot.data });
REC.n++;
if (REC.buf.length >= 8) await flush();
} catch (e) { console.log("capture error", String(e)); await sleep(100); }
}
await flush();
}
const ref = (snap, re) => { const line = snap.text.split("\n").find((l) => re.test(l)); const m = line && line.match(/\[ref=(e\d+)\]/); return m && m[1]; };
// Purple dot cursor: BrowserOS clicks do not move a visible mouse.
async function cursorTo(page, r) {
const node = await page.resolveRef(r);
const box = await page.cdp("DOM.getBoxModel", JSON.stringify({ backendNodeId: node.backendNodeId }));
const q = box.model.content;
const p = [(q[0] + q[4]) / 2, (q[1] + q[5]) / 2];
await page.evaluate((p) => {
let c = document.getElementById("__dc");
if (!c) {
c = document.createElement("div");
c.id = "__dc";
c.style.cssText = "position:fixed;z-index:2147483647;width:24px;height:24px;border-radius:50%;background:rgba(124,58,237,.3);border:2px solid #7c3aed;pointer-events:none;left:50%;top:50%;transform:translate(-50%,-50%);transition:left .6s ease,top .6s ease";
document.documentElement.appendChild(c);
}
c.style.left = p[0] + "px";
c.style.top = p[1] + "px";
}, p);
await sleep(750);
}
async function clickRe(page, re) {
const snap = await page.snapshot({ mode: "interactive" });
const r = ref(snap, re);
if (!r) throw new Error("no ref for " + re);
await cursorTo(page, r);
await page.click(r);
}
async function typeSlow(page, text) {
for (const word of text.match(/\S+\s*/g)) { await page.type(word); await sleep(60); }
}Body of a part:
const page = browser.page(TARGET_ID);
const rec = recLoop(22000);
const out = {};
try {
await sleep(800);
await clickRe(page, /button "Add attachment"/);
await clickRe(page, /MCP servers/);
await page.waitForText("Add MCP server");
// ...the steps of this shot, with short sleeps so a viewer can follow
} catch (e) { out.err = String(e); }
REC.on = false;
await rec;
out.frames = REC.n;
out.unsent = REC.buf.length;
if (REC.err) out.flushErr = REC.err;
return out;Tips:
- Put
page.gotobeforerecLoop. A slow load can push the run past 30 s. - A sign-in link opens a new tab. Read
browser.pages.list()before and after the click, then setREC.targetto the new page id. The tab can show as the user's tab. You can still capture it. - While the agent replies, record more 25 s parts. Stop when the snapshot
has no
Stop responsebutton. - One frame takes about 40 ms. A part gives about 15 frames per second.
- If
unsentis more than 0, the frame server did not get those frames. ReadflushErrandframe-server.log, fix the cause, and record the part again.
5. Check the frames
bun .agents/skills/record-demo/scripts/build-video.mjs segments "$REC/frames"Each line is one part. Open frames with Read at the start, middle and end of
each part. Look for:
- Images that did not load. A grey or blank box is a fail. To check an image in the page, draw it on a canvas and count its colours. A count of 1 is a placeholder. Example: a Canva thumbnail fetched while the design is still rendering is a flat grey PNG.
- Raw markdown or URLs that show while a reply streams.
- Dialogs and toasts that cover the step.
If a part is bad, record a fix part (for example a follow-up prompt), or leave the part out of the plan.
6. Build the MP4
Write $REC/plan.json. List the parts in play order. Speed up waits. Trim
the start of a part. Leave out bad parts.
{
"segments": [
{ "n": 1 }, { "n": 2 }, { "n": 3 },
{ "n": 5, "speed": [[0, 1], [7.5, 2]] },
{ "n": 6, "speed": [[0, 4]] },
{ "n": 10, "trim": 2.9 }
],
"maxFrame": 0.4,
"hold": 2.5,
"width": 1920
}maxFrame caps one frame's time on screen, which removes the gaps between
parts.
bun .agents/skills/record-demo/scripts/build-video.mjs build "$REC/frames" "$REC/plan.json" "$REC/demo.mp4"
bun .agents/skills/record-demo/scripts/build-video.mjs sheet "$REC/demo.mp4" "$REC/sheet.jpg" 6
ffprobe -v error -show_entries stream=codec_name,width,height -show_entries format=duration -of csv=p=0 "$REC/demo.mp4"Pass only if the codec is h264, and the contact sheet shows each shot in
order with no bad frames.
7. Deliver and clean up
- Send the MP4 with
SendUserFile(display: "render"). Give its full path. - Close the relay tab (
tabsactionclose). Stop the server:pkill -f record-demo/scripts/frame-server.mjs. - Leave the demo tabs open for the user.
- Report: the length, the shots, the parts you left out and why, and the data the demo changed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

