managing-demos
Skill0 starsChanged 9 days agoMITView on GitHub
Reviews and organizes the user's Demofy demos: lists recent demos, checks one demo's status and gets its video and share link, renames it, files it into a project, creates projects, turns public share links on or off, and stops or deletes a demo through Demofy's two-step confirmation. Use when the user asks 'what demos do I have', 'is the pricing demo done', 'give me the link to my last demo', 'share the onboarding video', 'put these demos in the Q4 launch project', 'rename this demo', 'stop that recording', or 'delete the old demo'. Reads freely; stopping and deleting cannot be undone, so they are confirmed first.
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
- making-demo-videosSkill
- managing-bookingsSkill
- managing-content-calendarSkill
- 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
8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
6
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_list_demos.
- Very specific: line 36
Call demofy:demofy_list_demos.
- Very specific: line 50
Call demofy:demofy_cancel_demo or demofy:demofy_delete_demo with its jobId.
- Very specific: line 52
Call the same tool again with the SAME arguments plus the confirmToken, in a new call.
- Distinctive: line 56
Never stop or delete without the user's explicit yes to a summary that names the demo.
- Very specific: line 57
Never include a confirmToken before the user has seen the demo it acts on, and never reuse one for a different demo or different arguments.
- Distinctive: line 58
Do not turn on a share link the user did not ask for.
≈ “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/managing-demos/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->Demofy: managing demos
Find the right demo, then report on it, share it, file it, or remove it without surprises.
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_list_demos. - Only
demofy:search_toolsanddemofy:execute_typescriptlisted (Code Mode, the default): calldemofy:search_toolsfirst, then call each tool insidedemofy:execute_typescriptasexternal_<tool>(for exampleexternal_demofy_list_demos); the program mustreturnits result. 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 NOT_FOUND: or CONFIRMATION_REQUIRED:.
Tools you will use
demofy:demofy_list_demos: the newest demos in the workspace, newest first, with id, title, status, kind and project. Whennextis not null there are older demos: call again withafterset to thatnext, unchanged.demofy:demofy_demo_status: one demo in full: its status, why it failed, any site it waits on, and once done thevideo(withdownloadUrl) andshareUrl.demofy:share_demo: turns a finished demo's public share link on (returns it) or off (the link stops working for everyone).demofy:demofy_rename_demo: renames a demo; an empty title restores the name Demofy derives.demofy:demofy_list_projects,demofy:create_project,demofy:demofy_move_to_project: projects (folders of demos) with their demo counts, a new project, and filing a demo under a project or none.demofy:demofy_cancel_demo: stops a demo that is still being made. It ends as stopped and cannot be resumed.demofy:demofy_delete_demo: deletes a demo and its video for good; its share link stops working and the allowance it used is not given back.
Workflow
Reviewing demos
- Call
demofy:demofy_list_demos. Follownextwithafteruntil you find what the user asked about, or tell them there are more. - List each demo with its title, status and project, and its page
https://app.demofy.io/jobs/<id>. Calldemofy:demofy_demo_statusonly for the demo the user cares about. - For a finished demo, give the video link. For a failed one, give the reason in plain words. For one waiting on a sign-in, use the
making-demo-videosskill to continue it.
Sharing, renaming and filing
- Identify exactly one demo by id. If several match, list them and ask which one.
- Sharing: call
demofy:share_demowithshared: trueand give theshareUrl; anyone with it can watch. Turning it off (shared: false) breaks the link for everyone who has it, so say that first. - Renaming: call
demofy:demofy_rename_demowith the new title. - Filing: call
demofy:demofy_list_projects, thendemofy:demofy_move_to_projectwith the project's id (ornullfor no project). If the project does not exist and the user wants it, calldemofy:create_projectfirst.
Stopping or deleting
- Identify exactly one demo and read it with
demofy:demofy_demo_status. - Call
demofy:demofy_cancel_demoordemofy:demofy_delete_demowith itsjobId. The first call does not act: it returnsCONFIRMATION_REQUIREDwith aconfirmToken(in Code Mode, a thrown Error whose message ends with that JSON). End that program there. - Show the user which demo (title, status, link) and what will happen: stopping throws away the run for good; deleting removes the video and its share link for good and does not refund the allowance. Wait for an explicit yes.
- Call the same tool again with the SAME arguments plus the
confirmToken, in a new call. The token works once and lasts 10 minutes; if it expired, start again at step 2. Report the result.
Rules
- Never stop or delete without the user's explicit yes to a summary that names the demo.
- Never include a
confirmTokenbefore the user has seen the demo it acts on, and never reuse one for a different demo or different arguments. - Do not turn on a share link the user did not ask for; a share link is public.
- For several demos, confirm each destructive call separately, one demo per confirmation.
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.

