Menu
Create, list, open, delete, and hand off MovScript production-bound editing workspaces. Use this for production-level editing workspace lifecycle only; after opening a workspace, switch to system_edit or remotion.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Configure and diagnose MovScript system management capabilities: providers, credentials, model catalog, route bindings, model gateway keys, generation tool server settings, ResourceAccessProfile/public tunnel/public backend settings, object relay/cloud file config, usage policy, and resource-access resolve/check diagnostics. Use only for explicit admin/system configuration tasks, not ordinary creative generation or editing.
Work with MovScript creative project state and product workflow boundaries using production-language first: project context, script, continuity references, story beats, shots, dialogue/narration voice, subtitles, sound/music, storyboard images, keyframe images, generated options, adoption decisions, external output return-to-Resource/Candidate flow, readiness checks, and impact review. Use when inspecting, changing, or reasoning about the underlying project source model through MCP tools.
Create MovScript MediaEditingProjects, edit timelines through Editing Service, run media-pipeline render/transcode/HLS tasks when available, preserve completed render/export artifacts as RawResources when possible, and avoid writing candidate decisions by default.
Generate MovScript creative outputs by calling generation tools: images, videos, voiceover, music, sound effects, subtitles, reference assets, storyboard images, keyframe images, and generated options. Before any generation tool executes, summarize the full generation context in user language and obtain explicit user confirmation. Also use when a user asks generically to generate text, images, video, or audio and the generation tool choice is unresolved, so Codex asks whether to use MovScript or another system before generating. Use internal content-production task, candidate, and selection project tools to preserve adoption gates, dependency checks, reference-shot inspection, generated artifact Resource preservation, and impact review.
Plan MovScript production work in plain production language: project context, screenplay/script source, production structure, story beats, continuity references, shots, dialogue voice, narration voice, subtitles, sound effects, music, storyboard images, keyframe images, generated results, and next-step triage when the user is unsure what to do. Use internal source entities and project tools only as implementation details.
Resolve MovScript project focus and project-management state through Project Service/runtime status before project-scoped work; open/fetch initialized projects, initialize or create projects only on explicit request, and orient agents to story/script context, production status, generated choices, and debug artifacts without exposing technical file structure to ordinary users.
| name | production-editing |
| description | Create, list, open, delete, and hand off MovScript production-bound editing workspaces. Use this for production-level editing workspace lifecycle only; after opening a workspace, switch to system_edit or remotion. |
| toolGrants | ["mcp__movscript__movscript_runtime_status","mcp__movscript__system_focus_get","mcp__movscript__domain_overview","mcp__movscript__domain_query_production_context","mcp__movscript__production_editing_resources_refresh","mcp__movscript__production_editing_workspace_list","mcp__movscript__production_editing_workspace_create","mcp__movscript__production_editing_workspace_get","mcp__movscript__production_editing_workspace_open","mcp__movscript__production_editing_workspace_delete"] |
Use this skill when the user wants to create, list, open, delete, or inspect production-bound editing workspaces.
This skill owns only the production-level lifecycle. It does not edit clips, tracks, Remotion source files, render commands, or candidate decisions.
Open ../domain/references/user-facing-response.md before ordinary workspace lifecycle replies so the user hears whether an editing workspace exists, what it is for, and what editing step comes next.
timeline_namespace owns story structure.ProductionEditingWorkspace owns concrete playback/editing structure for one production.system_editing and remotion.system_editing -> system_editremotion -> remotionproduction_editing_resources_refresh before create/open when the resource context matters.production_editing_workspace_list before creating a duplicate.production_editing_workspace_create using only kind: "system_editing" or kind: "remotion".production_editing_workspace_open.handoff.toSkill and switch to that skill for all concrete editing, preview, render, and diagnostics.MediaEditingProject from this skill.system_edit or remotion.