菜单
Use when the user asks "is trayce running", "trayce status", "check trayce", "what's trayce doing", or otherwise wants to know whether the trayce canvas server is currently up without starting or stopping it.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user asks to "set up trayce", "install trayce", "configure trayce", "remove trayce", or "uninstall trayce". Handles both installation (writing the MCP config into `.mcp.json` or `~/.claude.json`) and uninstallation. Prompts for scope (single project vs. all projects / global) when the user hasn't specified.
Use when the user wants to draw, sketch, or send visual content to this conversation via the trayce canvas. Also use when asked to push, send, or place images on a canvas. Triggers on mentions of drawing, sketching, canvas, visual, trayce, or pushing images.
Use when the user asks to "start trayce", "launch trayce", "run the canvas server", "start the canvas", or otherwise bring the trayce canvas server up. Use this skill after trayce has been configured via `trayce-setup` — not for first-time installation.
Use when the user asks to "stop trayce", "shut down trayce", "kill trayce", or "stop the canvas server".
| name | trayce-status |
| description | Use when the user asks "is trayce running", "trayce status", "check trayce", "what's trayce doing", or otherwise wants to know whether the trayce canvas server is currently up without starting or stopping it. |
| invocable_by | ["user"] |
Report whether the trayce canvas server is currently running. This skill is non-mutating — it does not start, stop, or restart anything.
bun run ${CLAUDE_PLUGIN_ROOT}/../scripts/status.ts
The script emits a single JSON line on stdout and exits 0 in all non-error cases so the output is always parseable.
Running:
{"running":true,"pid":12345,"port":9740,"url":"http://localhost:9740?token=…","token":"…"}
Report the URL, PID, and port to the user. The URL already embeds the auth token. If they want to open the canvas, they can paste the URL into a browser.
Not running — state file missing:
{"running":false,"reason":"no state file"}
Tell the user trayce is not running. If they want to start it, route to
trayce-start. If they've never configured trayce, route to trayce-setup
first.
Not running — stale state:
{"running":false,"reason":"stale state — pid 12345 not alive"}
The server crashed or was killed outside of trayce-stop. Tell the user the
state file is stale and suggest trayce-start to launch a fresh instance —
the start script will clean up the stale state file automatically.
Other running:false reasons ("corrupt state file", "no pid in state file", "jq not installed" from the .sh variant): relay the reason verbatim
and suggest trayce-start which recreates a clean state file.