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

81%

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

80%Weight 40%Scale 1-5

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

The body delivers concrete, executable guidance for authoring and editing `.canvas` bundles with clear workflows and validation guards, all tightly scoped to the single task with no external references needed. Minor improvements are possible in tightening the presentation section and adding an explicit manifest-edit feedback loop.

Suggestions

Add an explicit validate→fix→retry feedback loop for manifest edits (e.g., re-read `.canvas.json`, apply edits, then re-read to confirm no field was dropped before relying on it).

Tighten the "Show the result" section into a short ordered checklist so the several presentation imperatives are sequenced rather than bulleted.

Reduce redundancy between the opening paragraph and the frontmatter description (the board-vs-slides point is stated twice).

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept padding — tight bullets, an inline manifest example, and a specific shell command — but the opening paragraph reiterates the frontmatter's board-vs-slides point and the "Show the result" section restates some presentation guidance, leaving minor trimmable redundancy.	4 / 5
Actionability	Provides concrete executable guidance throughout (`read_file`/`write_file`/`edit_file`, `cp <scratch>/image-….png <board>.canvas/outputs/hero.png`, `surface_open` with `/poster.canvas`, full manifest JSON), covering the common cases with only minor gaps (no templated manifest-update code block, `surface_open` args prose-exemplified).	4.5 / 5
Workflow Clarity	Clear sequences for starting and updating a board with real validation checkpoints (re-read before editing to avoid clobbering; never open an empty or broken manifest), but the manifest-edit path lacks an explicit validate→fix→retry feedback loop and the "Show the result" section is a dense unnumbered set of imperatives.	4 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the single-purpose skill is well-organized under clear section headers with no nested references; it sits just above the simple-skill threshold (~85 lines) with one dense section that could conceivably be referenced out, keeping it just below the top anchor.	4.5 / 5
	Total	17 / 20 Passed

Description

83%Weight 40%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.

The description clearly states both capability and trigger conditions with concrete, domain-specific language and explicit routing guidance away from the sibling `slides` skill. It is strong on completeness and distinctiveness, with only minor gaps in action specificity and trigger-term breadth.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete actions ("Author and edit", "arranging visuals/design work spatially") with a clear object (a `.canvas.json` manifest plus placed document files), but does not enumerate the finer per-document actions (place/move/resize) that the body covers, sitting between the 1-2-action and several-action anchors.	3.5 / 5
Completeness	Explicitly answers both what ("Author and edit a Grida `.canvas` board — a `.canvas.json` manifest plus document files... placed on an infinite canvas") and when ("Use when working on a `.canvas` bundle or arranging visuals/design work spatially") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage including synonyms and a file extension ("`.canvas` bundle", "arranging visuals", "design work", "deck/presentation"), with a few common variations (e.g. "mood/art/reference board") missing, matching the good-but-not-exhaustive anchor.	4 / 5
Distinctiveness Conflict Risk	Clear niche (Grida `.canvas` infinite-canvas board) with active disambiguation against the related `slides` skill ("For a linear deck/presentation, use the `slides` skill instead"), though the broad phrase "design work" leaves slight overlap with generic design skills, placing it just below the minimal-conflict anchor.	4.5 / 5
	Total	17 / 20 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: 8ef5e53

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