SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsgridcraft-editor

gridcraft-editor

Office & productivity

View repository

Updated 11-04 23:02

About this skill

gridcraft embedded editor
  1. From the tool list of the currently loaded plugin, find the gridcraft-editor service. Call it using 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://gridcraft/panel.html. A text-only tool result does not mean the interface has been opened.
  3. When Codex does not automatically present the panel, call open_browser_editor, and hand the returned editorUrl to the host's built-in browser opening capability. Codex Desktop can call open_in_codex, with target as browser and url as the actual return value. Do not guess the local page path as a fixed port.
  4. Only one editing page is opened 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 edits in this round use 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 open_workbook/new_workbook to manage workbooks; read_range to inspect, set_cell to edit, execute_command with full commands; save_workbook to save.

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 in-host acceptance.

When the development candidate lacks ui/dist/adapter.mjs , you need to first build according to plugin ui/README.md . Do not guess paths from arbitrary caches, and do not bypass validation. This skill installed independently does not come with an 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 in 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 you cannot start another backend and claim it shares the session.

When done, save the project and reopen to check; read the actual exported file. Browser storage, preview screenshots, and submitted rendering tasks do not equal workspace delivery.