write-demo-script
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Turn one feature of Villain (poker trainer, getvillain.com) or Platework (private-chef management app) into a short, recordable screen-recording demo script for the ACTUAL app. Output: a pain-first hook, a shot-by-shot walkthrough (what to click/show, plus a voiceover line and an on-screen-text overlay per shot), a target length (30-60s vertical short-form by default; a longer landing-page hero cut on request), and a closing CTA to the landing page or waitlist. Every script shows the feature solving a real audience pain (poker-study pain for Villain; paperwork/admin/time pain for Platework), not a UI tour, and stays tight enough to film in one take. Use whenever the user says "write a demo script", "script a demo", "demo script for Villain/Platework", "script a walkthrough of", "film a demo of", "screen recording script", or otherwise wants a recordable walkthrough of a Villain or Platework feature. Pairs with research-trends and social-content. Not for app UI copy or non-demo marketing writing.
In this repository24 other files it gives its agents.
- anti-dark-codeSkill
- codex-reviewSkill
- condenseSkill
- db-checkSkill
- fable-modeSkill
- generate-visual-briefSkill
- graphifySkill
- grill-me-codexSkill
- grill-with-docs-codexSkill
- gws-calendarSkill
- gws-docsSkill
- gws-driveSkill
- gws-gmailSkill
- gws-sharedSkill
- gws-sheetsSkill
- impeccableSkill
- last30daysSkill
- notebooklmSkill
- pcdoctor-functional-testerSkill
- pc-doctorSkill
- persona-exec-assistantSkill
- research-trendsSkill
- social-contentSkill
- write-landing-copySkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
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.