agentleFS
Sign inStart free
ntaffziintaffzii/Skill-Agents/skills/obsidian/obsidian-canvas/SKILL.md

obsidian-canvas

Skill4 starsChanged 2 months agoMITView on GitHub

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.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 8
  2. Distinctive:

    Use file nodes for notes that already exist or should be created separately.

    line 59
  3. Distinctive:

    Use edges only for meaningful relationships.

    line 62
  4. Very specific:

    Use stable IDs such as edge-plan-build.

    line 64
  5. Distinctive:

    Ensure valid JSON, no trailing commas.

    line 67
  6. Distinctive:

    Ensure every edge references existing node IDs.

    line 68
  7. Distinctive:

    Ensure nodes do not overlap unintentionally.

    line 69
  8. Distinctive:

    Do not invent files unless the user asked to create them.

    line 73
  9. Distinctive:

    Prefer text nodes for new ideas and file nodes for existing notes.

    line 74
  10. Distinctive:

    Keep coordinates simple and grid-like.

    line 75

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Identify the canvas purpose
    • Map, timeline, workflow, dashboard, argument, project board, or concept graph.
  2. Choose layout
    • Left to right for process flows.
    • Top to bottom for hierarchy.
    • Hub and spoke for concept maps.
    • Columns for project boards.
  3. Create nodes
    • Use readable dimensions.
    • Keep text concise.
    • Use file nodes for notes that already exist or should be created separately.
  4. Connect edges
    • Use edges only for meaningful relationships.
    • Avoid visual clutter.
    • Use stable IDs such as edge-plan-build.
  5. 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free