Obsidian canvas

Skill ntaffzii/Skill-Agents/skills/obsidian/obsidian-canvas

Personal AI-agent skills, workflows, prompts, and setup guides for local LLMs and MCP-powered assistants.

Install

npx -y skills add ntaffzii/Skill-Agents --skill obsidian-canvas

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create and edit Obsidian JSON Canvas .canvas files with nodes, edges, groups, colors, links, files, and spatial layouts. Use when the user asks for an Obsidian canvas, visual map, knowledge graph, board, flow, or .canvas file.

SKILL.md

1.8 KB, as published. Nobody here has run it

Obsidian Canvas

Use this skill to create valid JSON Canvas files for Obsidian.

Canvas Shape

A canvas file is JSON with:

{
  "nodes": [],
  "edges": []
}

Nodes need stable IDs and position fields:

id
type
x
y
width
height

Common node types:

text with text
file with file
link with url
group with label

Edges connect node sides:

id
fromNode
fromSide
toNode
toSide

Workflow

Identify the canvas purpose
- Map, timeline, workflow, dashboard, argument, project board, or concept graph.
Choose layout
- Left to right for process flows.
- Top to bottom for hierarchy.
- Hub and spoke for concept maps.
- Columns for project boards.
Create nodes
- Use readable dimensions.
- Keep text concise.
- Use file nodes for notes that already exist or should be created separately.
Connect edges
- Use edges only for meaningful relationships.
- Avoid visual clutter.
- Use stable IDs such as edge-plan-build.
Validate JSON
- Ensure valid JSON, no trailing commas.
- Ensure every edge references existing node IDs.
- Ensure nodes do not overlap unintentionally.

Rules

Do not invent files unless the user asked to create them.
Prefer text nodes for new ideas and file nodes for existing notes.
Keep coordinates simple and grid-like.

Output Format

End with:

Canvas file created or changed
Node and edge count
Linked files referenced
JSON validation result