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

88%

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

Quality

Content

81%Scale 1-5

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

This is a well-crafted skill with excellent actionability and workflow clarity. Every node type has concrete JSON examples, workflows include explicit validation steps, and the validation checklist is thorough. The main weakness is moderate verbosity — some explanatory text and the 'When to Use' section could be trimmed, and the inline attribute tables make the document quite long, though they serve as useful reference material.

Suggestions

Trim the 'When to Use' section — Claude can infer when to use this skill from the frontmatter description and context.

Consider moving the detailed attribute tables to a separate reference file to reduce the main skill's token footprint while keeping the examples inline.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some content that could be tightened. The attribute tables are useful reference material but the 'When to Use' section and some explanatory text (e.g., 'Groups are visual containers for organizing other nodes') explain things Claude can infer. The layout guidelines table with suggested dimensions is helpful domain-specific knowledge, but overall the document is longer than necessary.	3 / 5
Actionability	The skill provides fully concrete, executable guidance with complete JSON examples for every node type and edges, specific attribute tables with types and defaults, exact ID format specifications, and a comprehensive validation checklist. All examples are copy-paste ready JSON.	5 / 5
Workflow Clarity	All four workflows are clearly sequenced with numbered steps and each ends with an explicit validation step. The validation checklist at the end provides a comprehensive feedback loop for error recovery, covering ID uniqueness, edge reference integrity, required fields, and JSON validity.	5 / 5
Progressive Disclosure	The skill references a separate EXAMPLES.md file for complete canvas examples, which is good progressive disclosure. However, no bundle files were provided to verify the reference exists. The main content is well-structured with clear sections, though the attribute tables and all node type details are inlined rather than being split into a reference file, which is borderline appropriate given the content length.	4 / 5
	Total	17 / 20 Passed

Description

95%Scale 1-5

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

This is a strong skill description that clearly communicates what the skill does and when to use it. It includes excellent trigger terms covering file extensions, use cases (mind maps, flowcharts), and the specific application context (Obsidian). The description is concise, uses proper third-person voice, and carves out a distinct niche with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists several specific actions: 'Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections.' This names the domain clearly and mentions concrete structural elements (nodes, edges, groups, connections), though it could elaborate more on specific operations like linking nodes, styling, or layout.	4 / 5
Completeness	Clearly answers both 'what' ('Create and edit JSON Canvas files with nodes, edges, groups, and connections') and 'when' ('Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian'). The 'Use when' clause is explicit with multiple concrete trigger scenarios.	5 / 5
Trigger Term Quality	Excellent coverage of natural trigger terms: '.canvas', 'visual canvases', 'mind maps', 'flowcharts', 'Canvas files', 'Obsidian', 'JSON Canvas'. Includes file extensions, synonyms, and the specific application context (Obsidian) users would naturally mention.	5 / 5
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: JSON Canvas / .canvas files specifically for Obsidian. The combination of file format (.canvas), application (Obsidian), and specific structural elements (nodes, edges, groups) makes this very unlikely to conflict with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/json-canvas/SKILL.md
Commit: debb2ec

Reviewed: 14 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.