Canvas

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — USE REQUIREMENTS DISCLOSED FIRST: this skill works on your own Obsidian vault and runs through the portable core of the claude-obsidian repository, scripts/claude-obsidian.py, which lives at the repository root OUTSIDE this skill's folder, together with the shared contracts it links to (under skills/wiki/references/ in that same product root, for example the provenance and operation-transaction contracts). Installing this listing copies only this skill's folder: without a full claude-obsidian installation (the core, its contracts, python3 to run it, and a selected user vault) the skill cannot run its transactions as designed. The family orchestrator is the separate wiki skill of the same repository. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Boards live in your vault under wiki/canvases/. One disclosed render-time exception: a canvas link node itself makes no request when created, but opening that board in Obsidian may fetch Open Graph metadata from the link URL's host; the skill says to disclose that and use a text node instead when that is not acceptable. Install "Canvas" for me. It creates, inspects and updates Obsidian Canvas boards (JSON Canvas 1.0) inside your vault: text, file, link and group nodes and edges between them, stored under wiki/canvases/ (wiki/canvases/main.canvas is only the default when you name no board). Status and list requests are read-only: it parses the selected .canvas files and reports node counts, group labels, broken edge endpoints and missing vault-relative file targets, and it does not create a missing default board during a status request. Every mutation is drafted first (vault-relative paths only; absolute paths, .. traversal and symlink escapes are rejected; only files already in the vault or created in the same reviewed transaction may be referenced), validated (unique IDs, integer geometry, existing edge endpoints), previewed, and applied as ONE claude-obsidian.transaction.v1 bundle of operation type canvas through the portable core, inspected first and applied only with the approval hash (APPROVAL_SHA256 pattern). The bundled references/canvas-spec.md is its fallback syntax source (it prefers a separately installed kepano/obsidian-skills json-canvas skill when present). The transaction engine creates and replaces files only: a board cannot be deleted or renamed through this skill, and destructive in-board edits (removing nodes or edges) need your explicit consent after the preview. It does not download or copy media assets, and it does not commit Git. Repository: https://github.com/AgriciDaniel/claude-obsidian (the skill is the whole skills/canvas/ folder at the pinned commit: SKILL.md, references/canvas-spec.md, 2 files in total) Pinned version: install the code at commit 2e545563172f97f02ecaaaab376ceea1246a0583 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/AgriciDaniel/claude-obsidian into a temporary folder, check out commit 2e545563172f97f02ecaaaab376ceea1246a0583, and copy the skills/canvas/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 6b406dc26079da1a000da167319bb9c7d947f6d98cf4e6d815b1480fc8b9957b - references/canvas-spec.md: SHA-256 a686534f3ad44983e29762d3d889ed3b86a00e7b2d4057689f11ff829805bfd5 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 2 files: SKILL.md and references/canvas-spec.md, its bundled JSON Canvas 1.0 syntax reference (read in full for this listing). The core it runs (scripts/claude-obsidian.py) and the transaction contract it links to live outside this folder, in the full claude-obsidian product root. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no board is created, read or changed. - At use time, reads are read-only and every mutation is one inspected transaction applied only with the approval hash (APPROVAL_SHA256 pattern), writing .canvas files under wiki/canvases/ in my vault (plus the optional _index.md catalog in the same bundle when it changes). A board file cannot be deleted or renamed through this skill. - No asset is downloaded or copied by the skill. The one network disclosure: creating an HTTPS link node makes no request, but opening the board in Obsidian may fetch Open Graph metadata from that URL's host; the skill says to disclose this beforehand or use a text node instead. - Do not create or edit any canvas, do not open any board in Obsidian, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole canvas folder into the agent's skills directory, in a folder named exactly "canvas", keeping its 2 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: canvas), the 2 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that a full claude-obsidian installation (portable core and contracts at the product root) and my own Obsidian vault are required to use it, that boards are written under wiki/canvases/ only through reviewed transactions, and that opening a board containing link nodes in Obsidian may fetch Open Graph metadata from those hosts). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.