making-demo-videos
Skill0 starsChanged 9 days agoMITView on GitHub
Makes a narrated product demo video in Demofy from a web address and a sentence of intent: sharpens the brief, picks optional voice, intro, outro, music and saved login, confirms with the user, starts the demo, follows it until the video is ready, and handles a pause for a site sign-in. Use when the user asks 'make a demo video of our pricing page', 'record a walkthrough of app.example.com showing how to invite a teammate', 'turn this URL into a product demo', 'film our signup flow with a voiceover', or 'is my demo ready yet'. Starts a recording that uses the plan's demo allowance, so it always confirms first.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nukeop/nucleartheir own version, first seen Oct 5, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nukeop/nuclear★ 19ksame name
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 repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adding-uptime-monitorsSkill
- analyzing-page-performanceSkill
- booking-meetingsSkill
- building-onboarding-workflowsSkill
- building-study-guidesSkill
- capturing-tasksSkill
- capturing-web-pagesSkill
- chasing-unpaid-invoicesSkill
- checking-domain-connectionsSkill
- checking-email-deliverabilitySkill
- checking-notification-deliverySkill
- checking-uptime-statusSkill
- cleaning-up-bookkeepingSkill
- connecting-customer-domainsSkill
- discussing-buildsSkill
- drafting-invoicesSkill
- drafting-social-postsSkill
- editing-demosSkill
- editing-page-draftsSkill
- extracting-document-textSkill
- finding-meeting-timesSkill
- handling-flaky-changesSkill
- investigating-tasksSkill
- managing-bookingsSkill
- managing-content-calendarSkill
- managing-demosSkill
- managing-voice-librarySkill
- planning-revisionSkill
- preflighting-domainsSkill
- publishing-pagesSkill
- reading-financial-reportsSkill
- reading-text-aloudSkill
- reading-web-pagesSkill
- reporting-snapvisor-usageSkill
- researching-course-materialSkill
- researching-summary-librarySkill
- responding-to-incidentsSkill
- reviewing-email-performanceSkill
- reviewing-notification-workflowsSkill
- reviewing-social-performanceSkill
- reviewing-visual-buildsSkill
- reviewing-workloadSkill
- searching-getitdone-api-docsSkill
- sending-email-campaignsSkill
- sending-notificationsSkill
- setup-bioflowSkill
- setup-calySkill
- setup-demofySkill
- setup-dodomainSkill
- setup-getitdoneSkill
- setup-notiflySkill
- setup-postifySkill
- setup-sendlySkill
- setup-shortySkill
- setup-snapvisorSkill
- setup-superbooksSkill
- setup-unotesSkill
- setup-upapiSkill
- setup-uptimelySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 0 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Every tool in this skill comes from the demofy MCP server, the Demofy connector, and is written here as demofy:<tool>.
- Very specific: line 15
Tools listed by name: call them directly, for example demofy:demofy_create_demo.
- Very specific: line 37
Only if the user asked for a voice, intro, outro or music, read demofy:demofy_list_voices or demofy:demofy_list_assets and use ids from …
- Very specific: line 39
After the yes, call demofy:demofy_create_demo once.
- Very specific: line 40
Check demofy:demofy_demo_status when the user asks, or every minute or so if they want to wait.
- Very specific: line 41
If needsSignIn lists a site, tell the user which site and why.
- Very specific: line 42
When the status is done, give the video link and, if the user wants to share it, call demofy:share_demo with shared: true and give the …
- Very specific: line 46
Never call demofy:demofy_create_demo without the user's explicit yes to the summary in step 4.
- Very specific: line 47
Never retry a failed demofy:demofy_create_demo blindly.
- Very specific: line 48
Never ask for a site password or one-time code in the chat.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated from plugins/demofy/skills/making-demo-videos/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->Demofy: making demo videos
Turn a page and an intent into a finished, narrated demo video, and bring back its link.
Connecting and calling the tools
Every tool in this skill comes from the demofy MCP server, the Demofy connector, and is written here as demofy:<tool>.
- Tools listed by name: call them directly, for example
demofy:demofy_create_demo. - Only
demofy:search_toolsanddemofy:execute_typescriptlisted (Code Mode, the default): calldemofy:search_toolsfirst, then call each tool insidedemofy:execute_typescriptasexternal_<tool>(for exampleexternal_demofy_create_demo); the program mustreturnits result. Batch independent reads withPromise.all. Validation and confirmation are identical on both surfaces. - "Tool not found": switch to the Code Mode route instead of retrying the direct call.
- No
demofytools at all: Demofy is not connected yet. Follow thesetup-demofyskill.
A refused call throws an Error whose message starts with its code, for example VALIDATION_ERROR:, QUOTA_EXCEEDED: or NOT_FOUND:, and any trailing JSON names the tool to call next.
Tools you will use
demofy:refine_prompt: rewrites a rough intent into the clearer brief Demofy records best, optionally for a URL. Creates nothing.demofy:demofy_list_voices,demofy:demofy_list_assets,demofy:demofy_brand_kit: narration voices, intro, outro, music and logo clips, and the workspace's default look. Read only when the user asks for a voice, an intro or outro, or music.demofy:demofy_list_connections: saved logins, sites Demofy can record signed in to.demofy:demofy_create_demo: starts the demo. Needsurl(the page to film) andprompt(what the demo should show). Optional fields includevoiceProfileId,introAssetId,outroAssetId,audioAssetId,connectionId,captions,formatandquality; read the exact shape fromdemofy:search_tools. Returns the new demo'sid,statusand its pageurl(relative tohttps://app.demofy.io).demofy:demofy_demo_status: where the demo is (queued, discovering, capturing, compositing, uploading, done, failed), why it failed, which sites it waits on (needsSignIn), and once done thevideoURLs andshareUrl.demofy:demofy_answer_sign_in: continues a demo paused for a sign-in, either without signing in to that site or behind a saved login.demofy:get_connect_links: a one-time link (15 minutes) the user opens in their own browser to sign in to a site and save the login.demofy:share_demo: turns the public share link of a finished demo on or off.
Workflow
- Get the page and the intent. The page must be a public
https://address; if the user gave only a product name, ask for the URL. If the intent is vague ("show the product"), calldemofy:refine_promptwith it and the URL, show the result, and let the user choose. - If the page is behind a sign-in, call
demofy:demofy_list_connections. Use a saved login for that site asconnectionId. If none exists, calldemofy:get_connect_linkswith the site, give the user the link and say what it does (they sign in there themselves and press Save), and continue oncedemofy:demofy_list_connectionsshows the login. - Only if the user asked for a voice, intro, outro or music, read
demofy:demofy_list_voicesordemofy:demofy_list_assetsand use ids from those lists. Otherwise leave them out; the workspace brand kit applies. - Show a summary and wait for an explicit yes: the URL, the brief, any voice, clips or saved login, and that it uses one demo from the plan's allowance and takes a few minutes.
- After the yes, call
demofy:demofy_create_demoonce. Give the user the demo page,https://app.demofy.io/jobs/<id>. - Check
demofy:demofy_demo_statuswhen the user asks, or every minute or so if they want to wait; never loop inside oneexecute_typescriptprogram. Report the stage in plain words. - If
needsSignInlists a site, tell the user which site and why. Then, with their choice: record without it (demofy:demofy_answer_sign_inwith a skip for that site), use a saved login for it (demofy:demofy_answer_sign_inwith thatconnectionId), or create one first withdemofy:get_connect_linksas in step 2. - When the status is
done, give the video link and, if the user wants to share it, calldemofy:share_demowithshared: trueand give theshareUrl. If it isfailed, report the error in plain words and offer to make it again with a clearer brief.
Rules
- Never call
demofy:demofy_create_demowithout the user's explicit yes to the summary in step 4. Each call starts a new recording and uses the allowance. - Never retry a failed
demofy:demofy_create_demoblindly. OnQUOTA_EXCEEDED, say the allowance is used up and offer the plan options (demofy:list_plans) instead of retrying. After aTOOL_FAILED, checkdemofy:demofy_list_demosbefore trying again, so the user does not get two demos. - Never ask for a site password or one-time code in the chat. The user signs in to other sites only through the
demofy:get_connect_linkspage. - Film only pages the user asked for. Do not add URLs, steps or claims they did not ask for to the brief.
- To edit, re-record, cancel or delete a demo, use the
editing-demosormanaging-demosskill.
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.

