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.
95
92%
Does it follow best practices?
Impact
100%
1.08xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is a well-crafted skill description that hits all the key criteria. It specifies concrete actions (create, edit), names the exact file format and extension (.canvas, JSON Canvas), lists structural components (nodes, edges, groups, connections), and provides explicit trigger guidance with natural user terms including the application context (Obsidian). The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections.' This names the format, file extension, and specific structural elements. | 3 / 3 |
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'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: '.canvas files', 'visual canvases', 'mind maps', 'flowcharts', 'Canvas files', 'Obsidian', and 'JSON Canvas'. Good coverage of both technical and natural language terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: JSON Canvas / .canvas files in Obsidian. The specific file format, extension, and application context (Obsidian) make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides comprehensive, actionable guidance for working with JSON Canvas files. The workflows are clearly sequenced with validation steps, examples are concrete and executable, and content is well-organized with appropriate progressive disclosure. The only minor weakness is some verbosity in areas where Claude's existing knowledge could be leveraged more (e.g., coordinate systems, basic JSON structure).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and well-structured, but includes some information Claude would already know (like what JSON is, how coordinates work) and the tables are somewhat verbose. The layout guidelines and suggested dimensions add useful domain-specific knowledge, but some sections could be tightened. | 2 / 3 |
Actionability | The skill provides fully concrete, copy-paste ready JSON examples for every node type and edges, specific attribute tables with types and defaults, exact ID format specifications (16-char hex), and precise spacing/sizing recommendations. Every section gives executable guidance. | 3 / 3 |
Workflow Clarity | All four workflows (create, add node, connect, edit) are clearly sequenced with numbered steps and each ends with an explicit validation checkpoint. The validation checklist at the end provides a comprehensive feedback loop for error detection and recovery. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-organized sections, references complete examples to a separate file (references/EXAMPLES.md), and links to the external spec. Content is appropriately split between the main skill file and referenced materials, with one-level-deep navigation. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- kepano/obsidian-skills
- Commit
fa1e131
- Reviewed
Table of Contents
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.