SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsfilmcraft-editor

filmcraft-editor

Design & creation

View repository

Updated 10-23 21:02

About this skill

filmcraft embedded editor
  1. From the tool list of the currently loaded plugin, find the filmcraft-editor service. Call it with the absolute path of this task's workspace: open_editor, passing on the first call workspace; relative file paths can be handed to the specific open tool once the editor is ready.
  2. When the host supports native MCP Apps, present ui://filmcraft/panel.html. A text-only tool result does not mean the interface has opened.
  3. When Codex does not automatically present the panel, call open_browser_editorand pass the returned editorUrl to the host's built-in browser open capability. Codex Desktop can call open_in_codexwith target set to browser and url set to the actual returned value. Do not guess a fixed port from the local page path.
  4. Open only one editor page per instance. Call editor_status, and wait until attached or ready is true before proceeding; if loading fails, handle the page error first.
  5. All editing in this round uses the same service. The native CLI and the web editor are not the same in-memory document; before switching, you must save and explicitly reopen.

Use command_list to read the current web engine commands; command_run executes on the visible page, and inspect verifies; open_file imports assets, list_files checks exports, and save_project or save_file writes to a new path in the workspace.

If the host only supports MCP, tool-calling capability and the embedded UI are two different things. The same editorUrl can be used in an external browser, but you must clearly state that this is not host-embedded acceptance.

When the development candidate is missing ui/dist/adapter.mjs , you must first build according to plugin ui/README.md . Do not guess paths from arbitrary caches, and do not bypass validation. Installing this skill independently does not include the editor service; you need to install the companion plugin or configure its MCP backend.

When the tool is not registered, after obtaining the plugin's actual directory you can run the following from the project terminal: node ui/dist/adapter.mjs --serve, specifying this task's workspace via the environment variable CRAFT_WORKSPACE_ROOT . Keep that process alive; this mode can display the UI, but automation must still connect to the corresponding MCP instance and must not start another backend and claim it shares the session.

When done, save the project and reopen it to check; read the actual exported files. Browser storage, preview screenshots, and submitted render jobs are not equivalent to workspace delivery.