json-canvas

Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.

100

1.08x

Quality

100%

Does it follow best practices?

Impact

100%

1.08x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is json-canvas in kepano/obsidian-skills

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured and high quality across all dimensions: lean and reference-style, fully actionable with executable examples, workflows with explicit validation checkpoints and feedback loops, and clean one-level-deep progressive disclosure to a real EXAMPLES.md bundle. It exemplifies the top anchor on each rubric dimension.

Dimension	Reasoning	Score
Conciseness	The body is a lean reference — attribute tables, executable JSON snippets, and targeted pitfalls (e.g. the newline \n vs \\n note) — with no library tutorials or over-explanation of concepts Claude already knows; every token earns its place.	3 / 3
Actionability	Provides complete, copy-paste-ready JSON node/edge objects, concrete ID-generation rules (16-char lowercase hex), and explicit positioning/spacing guidance rather than abstract direction.	3 / 3
Workflow Clarity	Four numbered workflows (Create, Add Node, Connect, Edit) each include an explicit Validate checkpoint, backed by an 8-item Validation Checklist and failure-recovery guidance — a clear sequence with feedback loops.	3 / 3
Progressive Disclosure	SKILL.md is a self-contained overview with a well-signaled one-level-deep pointer to the real references/EXAMPLES.md file (and external spec links), keeping full worked examples out of the main file as appropriate.	3 / 3
	Total	12 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, specific, and complete: it names concrete capabilities, provides natural trigger terms, includes an explicit Use-when clause, and occupies a distinct niche. It hits the top anchor on every dimension with no verbosity or over-claiming.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections" — matching the score-3 anchor of enumerating specific actions rather than vague language.	3 / 3
Completeness	Explicitly answers both what ("Create and edit ... with nodes, edges, groups, and connections") and when via an explicit "Use when ..." clause, hitting the score-3 anchor for both what AND when.	3 / 3
Trigger Term Quality	Covers natural user phrasing — ".canvas files", "visual canvases", "mind maps", "flowcharts", "Canvas files in Obsidian" — giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Obsidian JSON Canvas / .canvas files) with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: breferrari/obsidian-mind
Path: .claude/skills/json-canvas/SKILL.md
Commit: aa16349

Reviewed: about 15 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.