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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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

Quality

Content

65%

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

A thorough, highly actionable JSON Canvas reference whose weakness is token efficiency and structure: four redundant complete examples bloat it, and everything lives in one monolithic file with no progressive disclosure or explicit validation workflow.

Suggestions

Trim the four "Complete Examples" to one or two and remove overlap with the per-type examples above to recover token budget (conciseness).

Add an explicit create→validate→fix workflow that invokes the Validation Rules as a checkpoint loop, ideally for batch/large canvases (workflow_clarity).

Move the full spec reference and/or complete examples into a references/ file (e.g. EXAMPLES.md, SPEC.md) and link to it from a leaner overview (progressive_disclosure).

Dimension	Reasoning	Score
Conciseness	The body is largely domain-specific and accurate, but ~650 lines with four large "Complete Examples" (simple canvas, project board, research canvas, flowchart) overlapping the earlier per-type examples is heavy and could be tightened rather than earning a lean 3.	2 / 3
Actionability	Copy-paste-ready JSON node/edge definitions, per-type attribute tables, and an explicit eight-rule Validation Rules section give fully executable, concrete guidance.	3 / 3
Workflow Clarity	Validation rules are enumerated, but the skill is presented as a reference/spec rather than a sequenced create→validate→fix→retry workflow with explicit checkpoints, so it sits at the 2 anchor rather than 3.	2 / 3
Progressive Disclosure	Internal sectioning is clear, but the skill is a monolithic single file with no bundle references, and content that could be split (complete examples, full spec tables) is inline, matching the "content that should be separate is inline" 2 anchor.	2 / 3
	Total	9 / 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.

A strong, third-person description that pairs concrete capabilities with explicit "Use when" triggers and natural keyword coverage, occupying a clearly distinct niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Names concrete actions ("Create and edit JSON Canvas files") plus the specific building blocks manipulated ("nodes, edges, groups, and connections"), matching the multiple-concrete-actions anchor.	3 / 3
Completeness	Explicitly states what it does (create/edit .canvas with nodes/edges/groups/connections) and when to use it via an explicit "Use when..." trigger clause.	3 / 3
Trigger Term Quality	Covers natural user phrasing — ".canvas files", "visual canvases", "mind maps", "flowcharts", and "Canvas files in Obsidian" — giving broad keyword coverage users would actually say.	3 / 3
Distinctiveness Conflict Risk	The .canvas extension and Obsidian JSON Canvas niche form a clear, distinct trigger set unlikely to collide with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (657 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: anbeime/skill
Path: skills/obsidian-skills-integrated/json-canvas/SKILL.md
Commit: f595e96

Reviewed: about 13 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.