canvas lets Claude work with Obsidian .canvas files: list boards and their status, draft new nodes and edges, place vault notes, images and PDFs on a board, and group them into labelled zones.
Reads stay read-only. Any change is drafted as a preview, checked for valid JSON, unique IDs, existing edge endpoints and safe vault-relative paths, and applied only after you approve it.
What You Get
- Board status reports with node counts, groups, broken edges and missing files
- New or updated .canvas files with unique IDs and valid edge endpoints
- Notes, images and PDFs from the vault placed on a board inside labelled zones
- A preview of the exact changed paths before anything is written
- A catalog entry in wiki/canvases/_index.md when the vault keeps one
Common Use Cases
- Laying out a visual map of related notes as a knowledge board
- Adding a new note or image to an existing zone without disturbing the layout
- Checking a canvas for broken links before sharing the vault
What Makes It Unique
Most canvas helpers write JSON files directly. This skill preserves unknown JSON fields and node order, rejects absolute paths and traversal, accepts only HTTPS link nodes and warns that opening one in Obsidian may contact the host. All edits go through the plugin’s transaction engine, so a board change can be rolled back if it is interrupted.
Under The Hood
The skill is instructions plus a canvas format reference. Reading a board needs only file reads. For a change it runs the plugin’s Python core script through the shell to inspect and then apply a transaction bundle, and the write to the board file happens only in that step after your approval. It does not download assets or fetch web pages; a link node only stores a URL. It cannot delete or rename a board file.