cutscene-handoff
Skill13 starsChanged 24 days agoMITView on GitHub
Use when entering, skipping, interrupting, or leaving a cinematic can leave held input, camera, timescale, combat state, UI, or player control in the wrong state.
In this repository195 other files it gives its agents.
- llms.txtllms.txt
- hd-sprite-sequenceSkill
- pixel-animationSkill
- skin-weightsSkill
- spine-skeletalSkill
- sprite-atlasSkill
- sprite-catalogSkill
- sprite-skinSkill
- art-bibleSkill
- asset-pack-intakeSkill
- character-rigSkill
- materialsSkill
- model-pipelineSkill
- open-asset-fixtureSkill
- vfx-generateSkill
- a11y-controlsSkill
- ability-gateSkill
- action-feelSkill
- ad-breakSkill
- adventure-toolSkill
- aggro-tableSkill
- aim-assistSkill
- ammo-reloadSkill
- analytics-funnelSkill
- animation-blendSkill
- animation-graphSkill
- asset-runtimeSkill
- attack-tellSkill
- audio-busesSkill
- audio-feelSkill
- avatar-createSkill
- balance-designSkill
- boss-designSkill
- browser-inputSkill
- camera-anti-clipSkill
- camera-modestySkill
- camera-shotsSkill
- cert-handoffSkill
- chemistry-verbsSkill
- climb-vaultSkill
- cloud-saveSkill
- collision-layersSkill
- combo-designSkill
- cover-shooterSkill
- cover-spaceSkill
- crafting-loopSkill
- currency-dualSkill
- day-nightSkill
- death-carrySkill
- debug-slateSkill
- deck-buildSkill
- dialogue-beatSkill
- dialogue-flagsSkill
- difficulty-designSkill
- dodge-iframeSkill
- durability-economySkill
- encounter-designSkill
- enemy-aiSkill
- enemy-fireSkill
- enemy-kit-balanceSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Before takeover, snapshot or explicitly reset the play states the project needs: semantic held inputs, pointer/look capture, camera owner, …
- Distinctive: line 22
If a cinematic request arrives during hitstop, attack resolution, physics transition, save commit, or another unsafe logical boundary, …
≈ “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
Cutscene Handoff
This skill owns control/state transfer into and out of cinematics. It does not own tutorial goals, attack warnings, or pause policy.
Modes
| Mode | Skip policy |
| skippable | immediate authored skip action |
| hold-to-skip | hold gesture with progress/cancel semantics |
| first-play-locked | skip disabled only under an explicit first-play policy |
Handoff contract
Before takeover, snapshot or explicitly reset the play states the project needs: semantic held inputs, pointer/look capture, camera owner, UI context, timescale/pause source, and any gameplay transition token. Releasing control must not synthesize stale button edges or resume a stuck held action.
If a cinematic request arrives during hitstop, attack resolution, physics transition, save commit, or another unsafe logical boundary, queue it to the project's next safe boundary rather than imposing a universal ban on cinematics during combat.
Skip/complete handlers are idempotent. Duplicate skip, natural-end and scene-unload callbacks may race, but rewards, flags, camera restoration and control restoration happen once.
A cinematic that contains required warning/teaching information coordinates with attack-tell/tutorial-design; skip behavior must preserve the required gameplay contract by alternate presentation or authored policy.
Acceptance
Test natural completion, immediate/held skip, duplicate skip+end callbacks, focus loss, scene unload and takeover requested at an unsafe logical boundary. After handoff, one fresh input produces one valid action and camera/UI ownership is correct. Log takeover and restore reasons rather than judging from animation alone.
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.

