dotcanvas

Author and edit a Grida `.canvas` board — a `.canvas.json` manifest plus document files (references, generated images, notes) placed on an infinite canvas. Use when working on a `.canvas` bundle or arranging visuals/design work spatially. For a linear deck/presentation, use the `slides` skill instead.

Quality

92%

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

85%

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

The body is actionable and well-sequenced with explicit validation checkpoints and a clean section structure. Its only real weakness is mild verbosity and repeated framing in the presentation section. No bundle files exist to verify, so progressive disclosure was scored on the in-body organization.

Suggestions

Consolidate the conflicting framing in "Show the result" — pick one stance on whether presentation is a first milestone or auxiliary, rather than stating both — to tighten conciseness.

Trim over-qualified prose like "It is the durable, spatial home for a piece of work" that restates the description rather than adding new guidance.

Merge the repeated "do not wait / do not retry" admonitions into a single concise checklist of do/don't rules to cut redundant tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient — manifest shape, layout semantics, and concrete `cp` commands without explaining concepts Claude knows — but the "Show the result" section repeats overlapping guidance ("Treat presentation as the first production milestone" alongside "Treat presentation as auxiliary") and could be tightened, matching the mostly-efficient-but-could-be-tighter anchor.	2 / 3
Actionability	Provides fully executable guidance — `read_file`/`write_file`/`edit_file`, `cp <scratch>/image-….png <board>.canvas/outputs/hero.png`, `surface_open` with a concrete `/poster.canvas` example, and a complete manifest JSON block — so it is copy-paste ready.	3 / 3
Workflow Clarity	Sequences the work clearly (make the bundle folder first, write the manifest, for existing boards read first to preserve fields) and includes explicit validation gates ("Never open an empty bundle or a broken manifest"; re-read before editing to avoid clobbering), matching the clear-sequence-with-checkpoints anchor.	3 / 3
Progressive Disclosure	A single self-contained SKILL.md with well-organized sections (Structure, Working pattern, Show the result) and no nested references — the only pointer ("see the `slides` skill") is one level and cross-skill — so it organizes content appropriately without a monolithic wall of text.	3 / 3
	Total	11 / 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 specific, gives explicit when-to-use triggers, and proactively disambiguates against the slides skill. It uses third-person voice with no first/second-person phrasing. It is concise yet complete.

Dimension	Reasoning	Score
Specificity	Names concrete actions ("Author and edit a Grida `.canvas` board") and concrete artifacts ("a `.canvas.json` manifest plus document files (references, generated images, notes) placed on an infinite canvas"), matching the multiple-specific-actions anchor rather than the domain-plus-some-actions anchor at 2.	3 / 3
Completeness	Explicitly answers what (author/edit a manifest-plus-documents board) and when via a clear "Use when working on a `.canvas` bundle or arranging visuals/design work spatially" trigger, satisfying both halves per the anchor.	3 / 3
Trigger Term Quality	Includes natural user phrasing — "arranging visuals/design work spatially" and "working on a `.canvas` bundle" — giving good coverage of terms a user would say, though lightly spiced with Grida/.canvas jargon it still lands above the missing-common-variations anchor at 2.	3 / 3
Distinctiveness Conflict Risk	Actively disambiguates from the closest competing skill ("For a linear deck/presentation, use the `slides` skill instead") and carves a clear infinite-canvas/spatial niche, so it is unlikely to trigger for the wrong skill.	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: gridaco/grida
Path: skills/dotcanvas/SKILL.md
Commit: 2e0d276

Reviewed: 3 days 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.