菜单
Handle Chat-only Canvasight Run output in the current Codex thread. Use when a Run arrives through the native widget host bridge, when a browser/dev Run is queued for await_canvasight_run fallback, or when legacy Plan or Goal node data must be treated as Chat.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Niall-Young/Canvasight --skill canvasight-run命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Create, refine, or replace Canvasight graphs through write_canvasight_graph; combine professional content Skills with Canvasight's validated horizontal graph structure; and assign explicit or clearly matched Skills to individual Task Nodes. Use when the user asks Codex to generate or update Canvasight nodes, Asset Nodes/资产节点, promote attachments/附件提升, create Groups/分组, write to the canvas/用画布/放到画布/写到画布, visualize product or UX intent, map an article or research topic, analyze a codebase into a graph, turn work into an execution map, reuse Canvasight node templates, create/update .scatter/scatter.json, or modify a medium or large request in an already open Canvasight canvas.
Canvasight plugin index. Use when the user explicitly mentions Canvasight or Scatter, says 打开画布 / 打开 Canvasight, asks @Canvasight to generate an image into the canvas, and the request spans multiple Canvasight workflows, or when a Canvasight canvas is already open/attached and a later request is ambiguous or large enough to decide whether it should route through graph writing before direct execution.
Generate new raster images with Codex imagegen and add every final result to the active Canvasight Page as a managed Asset Node. Use when the user invokes @Canvasight or otherwise asks to generate, create, draw, or render a new image directly into Canvasight. Do not use for editing an existing Canvasight Asset in place.
基于 SOC 职业分类
正在显示 SKILL.md
| name | canvasight-run |
| description | Handle Chat-only Canvasight Run output in the current Codex thread. Use when a Run arrives through the native widget host bridge, when a browser/dev Run is queued for await_canvasight_run fallback, or when legacy Plan or Goal node data must be treated as Chat. |
Use this skill to handle Canvasight Run payloads as Chat follow-ups.
claim_canvasight_thread before clicking Run in an old tab so the daemon scopes the queued Run to the current thread. A bare 5173 page without an explicit claim must be treated as unbound, not as a sent Run.await_canvasight_run. If await_canvasight_run is not callable, use tool_search for Canvasight tools first. If it is callable but fails with Transport closed, report canvasight_mcp_transport_closed: the fallback queue cannot be consumed from this stale task. Inspect mcp-lifecycle.log when available, then reload or use a new task with current Canvasight tools.sessionId when available; use projectPath to attach to the next queued Run from any active session in that project.structuredContent as the source of truth for the next Codex action.structuredContent.agentTeam.enabled is true, use canvasight-agent-team before executing the task. Read its schema and ROSTER.md before assigning or rebuilding a role.Normal Canvasight Run delivery must come from the Codex native widget host bridge, using either MCP Apps ui/message or Codex/OpenAI compatibility window.openai.sendFollowUpMessage. If the UI reports browser_fallback_no_bridge, the page was opened through browser fallback/dev URL instead of the native widget; reopen with open_canvasight after tool_search, or receive the queued fallback with await_canvasight_run. If those visible Canvasight MCP tools fail with Transport closed, stop, inspect mcp-lifecycle.log, and report canvasight_mcp_transport_closed instead of promising queued recovery in the same stale thread. Browser URLs and bare dev pages must not silently pretend success: if no claim exists, the UI must report unbound_dev_session; otherwise it queues the payload for await_canvasight_run. Do not treat Codex app-server turn/start as a Run delivery path.
Native open must have received the active task's explicit CODEX_THREAD_ID and passed the instance-bound await gate with verified fullscreen React/project/canvas evidence; Run is accepted only from that same instance. Do not use a missing hostCapabilities.message declaration alone to disable Run after the MCP App handshake succeeds. Call sendMessage and treat only its resolved Promise as sent.
Read references/run-output-contract.md for Chat delivery and legacy-node normalization.