wassermanproductions/master-canvas-hermes-plugin / skills/handoff
handoff
VerifiedWork with Master Canvas AI video handoff packages. Use when a user provides a Master Canvas ZIP or project_manifest.json and wants Hermes to inspect assets, preserve scene and shot order, prepare ComfyUI/LTX 2.3 jobs, or hand off prompts to Kling, Veo, or another video generation operator. Also use when a user wants Hermes to autonomously create, update, and package a Master Canvas pre-production project from a brief, scenes, shots, prompts, references, and local assets.
Master Canvas Handoff
Use this skill when a user gives Hermes a Master Canvas handoff ZIP, extracted package folder, or project_manifest.json and wants video-generation work planned or executed from that package.
Also use it when the user wants Hermes to operate Master Canvas autonomously. In that mode, Hermes should create and maintain a Master Canvas-compatible package directly: scenes, shots, prompts, negative prompts, copied assets, references, ComfyUI/LTX jobs, Kling/Veo prompt sheets, and deliverable bins.
Default Workflow
- Inspect the package with
mastercanvas_inspect_package. - If the package is a ZIP and generation work will happen locally, extract it with
mastercanvas_extract_package. - Build the ComfyUI/LTX plan with
mastercanvas_comfy_plan. - Treat
project_manifest.jsonas the source of truth for scene order, shot order, prompts, negative prompts, references, and output bins. - Keep outputs organized by scene using
deliverables/bin_plan.jsonor theoutputBinfields in the plan.
Autonomous Master Canvas Workflow
When the user wants Hermes to create or manage a Master Canvas project:
- Use
mastercanvas_create_packageto create the package from the brief, scene list, shot list, prompts, and local asset paths. - Use
mastercanvas_upsert_scenewhen the user changes the scene structure, scene description, style prompt, or music prompt. - Use
mastercanvas_upsert_shotwhen the user adds or changes a shot, source image, prompt, negative prompt, camera direction, lens, lighting, duration, or notes. - Use
mastercanvas_inspect_packageafter changes to confirm scene count, shot count, missing assets, and readiness. - Use
mastercanvas_package_zipwhen the package is ready to share, archive, or send into downstream generation.
In autonomous mode, keep the package compatible with the Master Canvas app handoff contract. Do not invent a separate schema unless the user explicitly asks for a different format.
Package Contract
Expected Master Canvas handoff packages usually contain:
project_manifest.json: complete project context, scene list, shot list, asset list, prompt fields, negative prompt fields, and generation targets.assets/: source images, uploaded video references, uploaded music/audio references, and other media.comfyui/jobs/: one JSON job per shot when exported by Master Canvas.kling-veo/: prompt sheets for operators using hosted generation tools.hermes-agent/: agent-facing brief and context notes.deliverables/bin_plan.json: target folder/bin structure for completed renders.
If one of these folders is missing, continue with the manifest and explain the limitation.
ComfyUI / LTX 2.3 Execution Guidance
When the user wants ComfyUI/LTX:
- Preserve the shot sequence exactly.
- Use the image path from
sourceImageas the first-frame/image reference for each shot. - Use the provided prompt and negative prompt without dropping lens, lighting, action, continuity, or sound notes.
- Target at least 1080p unless the manifest specifies a higher floor.
- Generate each shot into its scene bin.
- Return an inventory of completed shots grouped by scene.
- Flag missing assets, impossible prompt requirements, or continuity conflicts before starting expensive generation.
Kling / Veo Operator Guidance
When the user wants Kling, Veo, or a human operator handoff:
- Use the Kling/Veo prompt sheet if present.
- Otherwise build a simple table with scene, shot order, source asset path, prompt, negative prompt, duration, and notes.
- Keep file names and output bins stable so rendered clips can be reconciled against the original canvas.
Verification
Before reporting completion:
- Confirm total scenes and shots.
- Confirm whether any shots are missing source images.
- Confirm where extracted assets or output bins are located.
- Summarize the next concrete generation step.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |