How do I install the Canvas Comments skill?

Run npx skillmds@latest add fusedio/canvas-comments in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Canvas Comments safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Canvas Comments?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Canvas Comments free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Canvas Comments?

fusedio (@fusedio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Canvas Comments by fusedio — Agent Skill

Name: Canvas Comments
Author: fusedio

Canvas Comments

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.

fusedio Updated Sep 21, 2026

File contents

Fused canvas comments ([[comments]] in canvas.toml)

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.

Read: find the work

Get the canvas locally: fused workbench canvas pull <name> -o <dir> (or use the folder you have).
Every [[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.

Resolve: the full contract (all four steps, not just status)

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.

Write: adding a new comment

[[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 reference (snake_case in TOML — never camelCase)

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.

Verify, then push

fused workbench canvas validate <dir>        # structure check
fused workbench canvas push <dir> --canvas <name>

Common mistakes

Resolving without resolved_by = "ai" / resolved_at / a reply (the #1 miss).
camelCase keys (createdAt) in TOML — the parser ignores them; data silently lost.
Anchoring by node id instead of anchor_udf name.
Marking resolved without actually making the code change the comment asks for.
Editing/deleting other people's ids or created_ats — append, don't rewrite history.

---name: canvas-commentsdescription: 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.---# Fused canvas comments ([[comments]] in canvas.toml)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.## Read: find the work1. Get the canvas locally: `fused workbench canvas pull <name> -o <dir>` (or use the folder you have).2. Every `[[comments]]` block where `status = "open"` is an actionable request.3. `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.## Resolve: the full contract (all four steps, not just status)After actually making the fix the comment asks for:```toml[[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 UIresolved_at = 1749600200000 # 3. ms epoch timestamp (date +%s000)[[comments.replies]] # 4. say what you didid = "reply-<unique>"content = "Changed the default to 7. Done."created_at = 1749600200000created_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.## Write: adding a new comment```toml[[comments]]id = "cmt-<unique>" # required, stable, unique in filex = 120.0 # required: canvas coords (floats)y = 80.0anchor_udf = "process_data" # optional: node NAME (matches a [[canvas.nodes]] udfName)offset_x = 24.0 # only meaningful with anchor_udfoffset_y = 16.0content = "non-empty text" # blank content is silently droppedstatus = "open"created_by = "ai" # REQUIRED when you author itcreated_at = 1749600000000 # ms epoch```## Field reference (snake_case in TOML — never camelCase)| 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.## Verify, then push```bashfused workbench canvas validate <dir> # structure checkfused workbench canvas push <dir> --canvas <name>```## Common mistakes- Resolving without `resolved_by = "ai"` / `resolved_at` / a reply (the #1 miss).- camelCase keys (`createdAt`) in TOML — the parser ignores them; data silently lost.- Anchoring by node id instead of `anchor_udf` name.- Marking `resolved` without actually making the code change the comment asks for.- Editing/deleting other people's `id`s or `created_at`s — append, don't rewrite history.

Frequently asked questions