json-canvas

Create and edit JSON Canvas files with valid nodes and edges.

Updated May 18, 2026
One-click install
npx skills add https://github.com/Noegnesis/noesis --skill json-canvas-noegnesis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: json-canvas
Source: https://github.com/Noegnesis/noesis/tree/main/skills/json-canvas
Command: npx skills add https://github.com/Noegnesis/noesis --skill json-canvas-noegnesis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of creating and maintaining structured JSON Canvas files in Obsidian without breaking node/edge relationships or JSON validity.

Core Features & Use Cases

  • Create canvases from the JSON Canvas spec: Generate the required top-level structure and add nodes/edges.
  • Edit existing canvases safely: Add, connect, or update nodes and edges while preserving unique IDs and valid references.
  • Validate canvas integrity: Ensure JSON parses correctly and that every fromNode/toNode edge points to an existing node.
  • Use cases: mind maps, flowcharts, project boards, and visual planning artifacts stored as .canvas files in your Obsidian vault.

Quick Start

Create a new mind-map style .canvas file in Obsidian with several text nodes connected by edges, then validate that all node IDs and edge references are consistent and the JSON is parseable.

Frequently Asked Questions about json-canvas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create valid JSON Canvas files for Obsidian?

To create valid JSON Canvas files for Obsidian, generate the required top-level structure with unique 16-character hex IDs for nodes, correct required fields per node type, and valid edge references connecting existing nodes.

How do I safely edit an existing .canvas file without breaking node and edge relationships?

Safely editing a .canvas file requires adding or updating nodes and edges while preserving unique IDs, ensuring every fromNode and toNode edge reference points to an existing node, and running post-change JSON parsing validation.

What is the JSON Canvas 1.0 structure required for Obsidian workflows?

The JSON Canvas 1.0 structure requires a specific top-level format containing nodes and edges, where each node has a unique 16-character hex ID and correct required fields based on its specific node type.

Can I use this to build mind maps and flowcharts in Obsidian?

Yes, you can build mind maps and flowcharts in Obsidian by generating .canvas files with text nodes connected by labeled edges, then validating that all node IDs and edge references are consistent and parseable.

How do I validate canvas integrity and ensure my JSON parses correctly?

To validate canvas integrity, ensure the JSON parses correctly and verify that every fromNode and toNode edge points to an existing node within the canvas document structure.

Why does my Obsidian canvas break when I add new nodes to the JSON?

Obsidian canvas JSON breaks when node integrity is compromised by duplicate 16-character hex IDs, missing required fields for specific node types, or edge references pointing to non-existent nodes.