← ClaudeAtlas

film-game-productionlisted

Operate Vixel Film media through the Film v1 MCP contract. Use when the user asks to make a film, images or videos in a Vixel Work, inspect Vixel credits and Jobs, upload references, or review results in their Vixel studio. Use the website for adoption, Timeline editing, export and publishing.
Vixel-AI/vixel-plugins · ★ 0 · AI & Automation · score 62
Install: claude install-skill Vixel-AI/vixel-plugins
# Vixel Film media The skill path is retained for existing installations; this version uses Film v1 tools, not the retired Canvas film-game contract. Reconnect with `film.read`, `film.write`, `film.generate` and optional `offline_access`. Mixed Film/Creator grants select the Film registry; use a separate legacy connection if needed. ## Choose and author the same Work Use `film_v1_projects` to list owned Works and `film_v1_project` with an explicit `projectId` to read the current revision, documents, scenes, Elements, Shots, assets and Timeline. Resume an existing Work when requested. For a new film, `film_v1_project_create` accepts title, premise, aspectRatio and a stable `idempotencyKey`; it creates an empty Work within the website's account allowance and returns its canonical state and webUrl. It performs no text/media generation. After saving the Script, `film_v1_story_save` writes the complete scenes array; `film_v1_plan_save` writes complete elements and shots arrays. Both require `projectId`, `expectedRevisionId`, `expectedWriteVersion` and `idempotencyKey`. Read before editing; preserve every unrelated scene/Element/Shot. Tool input schemas describe writable fields; do not send the full read model as input. The initial plan requires a saved canonical Script. Story/Plan writes are direct creator-authorized edits, not approval of media, a new production run, or proof of an approved Director proposal. Read back returned receipts and current state. On unknown outcomes