菜单
Use when a Fused canvas.toml contains (or needs) a [[comments]] block — e.g. the user asks to check/fix/resolve canvas comments, review feedback pins on a canvas, or leave comments on a canvas for someone else. Covers reading, writing, and resolving comments via the fused CLI pull/push workflow.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Authoring standalone HTML artifacts — `scripts/<name>/main.html` documents that Fused and Flow serve full-bleed and wire to a `window.fused` runtime (callUdf / runSql / params). Use when the output of a project is a bespoke interactive HTML page — a custom chart, a form, a report, a small app — that calls UDFs and runs SQL directly, rather than a JSON-UI widget. Covers the `window.fused` API, the `{{ref}}`/`$param` data grammar, load-order gotchas, host differences, and how the artifact gets rendered in front of a human.
Show the human a real browser UI — to ask a question, get an approval/decision, or review a plan — built from Fused's JSON-UI primitives and opened with `fused widget open` (one-shot — inline `--config` or a `.json` file) or the parley (`widget push`/`widget watch`, standing). Use in Claude Code whenever a structured choice, form, approval, or plan review would be clearer than plain terminal text, and you want the human's answer back as JSON. If the task touches an existing project, UDF, or data-bound widget (anything with `{{ref}}`/`sql`), also load `fused-projects` and `fused-widgets` first.
Reference for the fused CLI — environment management, file storage, secrets, code execution, and infrastructure commands. Use when writing or explaining shell commands that invoke `fused`, or when helping users set up, switch between, or provision environments. If the commands are part of building or running a project, load `fused-projects` first for the end-to-end model.
Authoring and previewing JSON-UI widgets as the response of running a project — the py-UDF-computes → json-widget-visualizes pattern, the {{ref}}/$param data grammar, how resolution runs through the compute backend, and the CLI surfaces (widget open, parley, deployed URL) that put a rendered widget in front of a human. Use whenever the desired output of a UDF/project is a widget, not raw data.
Best practices for running code through fused's execute_code tool. Use when writing or reviewing any mcp__openfused__execute_code call — covers how to structure user code, choose a data library, handle results, and write outputs to the file store. For security scanning, spec checks, and testing see fused-verify. If this is part of building or running a project, load `fused-projects` first for the end-to-end model (and `fused-widgets` if the result is a rendered UI).
The fused storage and secrets MCP tools — inspecting cloud-native datasets and managing secrets. Use when finding/listing/counting S3 objects, reading a Parquet/Arrow/CSV schema, minting a download URL, uploading content, or storing/reading/deleting secrets, via mcp__openfused__{list_files,count_files,get_file,get_file_schema,upload_file,get_secret,put_secret,list_secrets,delete_secret}. For running code over the data see fused-execute; for the equivalent CLI commands see fused-cli. If this is a step in building or running a project, load `fused-projects` first for the end-to-end model.
| name | canvas-comments |
| description | Use when a Fused canvas.toml contains (or needs) a [[comments]] block — e.g. the user asks to check/fix/resolve canvas comments, review feedback pins on a canvas, or leave comments on a canvas for someone else. Covers reading, writing, and resolving comments via the fused CLI pull/push workflow. |
Pinned comment threads on a Fused canvas serialize as top-level [[comments]] blocks in canvas.toml. Comments with status = "open" are your work queue; resolving one is a three-field contract plus a reply, so the Workbench UI correctly attributes the work to AI.
fused workbench canvas pull <name> -o <dir> (or use the folder you have).[[comments]] block where status = "open" is an actionable request.anchor_udf = "<udfName>" tells you WHICH node it's about — the fix belongs in <udfName>.py (or .json/.md/.html with that stem). No anchor_udf ⇒ canvas-level comment; read content for scope.After actually making the fix the comment asks for:
[[comments]]
id = "cmt-a" # never change existing ids
# ...existing fields stay untouched...
status = "resolved" # 1. was "open"
resolved_by = "ai" # 2. REQUIRED — this is what shows the AI badge in the UI
resolved_at = 1749600200000 # 3. ms epoch timestamp (date +%s000)
[[comments.replies]] # 4. say what you did
id = "reply-<unique>"
content = "Changed the default to 7. Done."
created_at = 1749600200000
created_by = "ai" # REQUIRED on AI-written replies
Setting only status = "resolved" is wrong — without resolved_by = "ai" the UI cannot attribute the resolution, and without a reply the user doesn't know what changed.
[[comments]]
id = "cmt-<unique>" # required, stable, unique in file
x = 120.0 # required: canvas coords (floats)
y = 80.0
anchor_udf = "process_data" # optional: node NAME (matches a [[canvas.nodes]] udfName)
offset_x = 24.0 # only meaningful with anchor_udf
offset_y = 16.0
content = "non-empty text" # blank content is silently dropped
status = "open"
created_by = "ai" # REQUIRED when you author it
created_at = 1749600000000 # ms epoch
| Field | Notes |
|---|---|
id, content, x, y | required; blank/whitespace content ⇒ row dropped on parse |
status | open | resolving | resolved; omitted ⇒ open |
anchor_udf, offset_x, offset_y | anchor by UDF name, not node id; unknown name ⇒ anchor silently dropped |
created_by, resolved_by | "user" | "ai"; omitted = user |
created_at, updated_at, resolved_at | ms epoch integers |
replies | [[comments.replies]] with id, content, created_at, optional updated_at, created_by |
Never write a TOML null/empty value — omit absent fields entirely. Comments sort by created_at on export; don't reorder blocks by hand.
fused workbench canvas validate <dir> # structure check
fused workbench canvas push <dir> --canvas <name>
resolved_by = "ai" / resolved_at / a reply (the #1 miss).createdAt) in TOML — the parser ignores them; data silently lost.anchor_udf name.resolved without actually making the code change the comment asks for.ids or created_ats — append, don't rewrite history.