AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Obsidian Canvas

skill-ntaffzii-skill-agents-obsidian-canvas · by ntaffzii

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.

↗ Website ↗ Repository
— No reviews yet
0 installs
18 views
0.0% view→install

Install

$ agentstack add skill-ntaffzii-skill-agents-obsidian-canvas

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Obsidian Canvas? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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.
  1. Choose layout
  • Left to right for process flows.
  • Top to bottom for hierarchy.
  • Hub and spoke for concept maps.
  • Columns for project boards.
  1. Create nodes
  • Use readable dimensions.
  • Keep text concise.
  • Use file nodes for notes that already exist or should be created separately.
  1. Connect edges
  • Use edges only for meaningful relationships.
  • Avoid visual clutter.
  • Use stable IDs such as edge-plan-build.
  1. 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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in AI & ML