docs-canvas

Author and manage user-facing documentation for the Grida Canvas editor. Covers writing style, tone, product screenshots, demo state preparation, and content structure for pages under docs/editor/. Use when creating or editing canvas editor documentation, capturing screenshots of canvas features, or planning visual demos. Trigger phrases: "write user docs", "document this feature", "screenshot for docs", "canvas user guide", "update help page".

Quality

95%

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

93%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.

A lean, highly actionable skill body: exact commands, templates, and specs with no filler, and good delegation of detail to docs/AGENTS.md and the docs-svg-kit skill. The only gap is the absence of an explicit error-recovery loop and a single ordered end-to-end workflow, which keeps workflow clarity just below the top anchor.

Suggestions

Add a short ordered end-to-end workflow (draft page → prepare demo state → capture/crop screenshot → run pre-publish checklist → verify render) so the sections read as one sequenced process.

Extend the Pre-Publish Checklist with a brief failure path, e.g. "if the page fails to render or links are broken, fix and re-run `pnpm --filter docs start` before publishing", to close the feedback loop.

Name the trigger context explicitly in one or two of the trigger phrases (e.g. "canvas user guide" is good; add canvas to "write user docs") to reduce conflict risk noted by the description judge.

Dimension	Reasoning	Score
Conciseness	The body is dense with project-specific facts (build commands, 960x960 WebP specs, universal routing links, MDX caveats) and spends nothing on concepts Claude already knows; there is no padding anywhere. Anchor 5 fits: every token earns its place.	5 / 5
Actionability	Guidance is copy-paste ready: exact commands ("turbo build --filter=editor && turbo start --filter=editor", "pnpm --filter docs start"), a full page-structure markdown template, exact file naming/format specs, URL parameters (?src=, ?backend=canvas\|dom), and a scripted demo-state API (globalThis.grida). Concrete specifics cover the common cases.	5 / 5
Workflow Clarity	The demo-state workflow is explicitly ordered with a fallback chain (fixture → scripting → URL params → manual) and the Pre-Publish Checklist provides validation endpoints ("Page renders: pnpm --filter docs start", "verify screenshots match current UI"). Falls short of anchor 5 because there is no explicit feedback loop — no instruction on what to do when the render check or a checklist item fails — and no single end-to-end sequence tying writing, screenshots, and publishing together; clearly above anchor 3 since checkpoints are present.	4 / 5
Progressive Disclosure	This is a self-contained, well-sectioned overview that appropriately delegates detail one level deep: linking rules/MDX caveats to docs/AGENTS.md and the entire SVG-figure toolkit to the docs-svg-kit skill instead of inlining it. Structure matches anchor 5: clear overview, well-signaled one-level references, easy navigation.	5 / 5
	Total	19 / 20 Passed

Description

96%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.

A strong description that explicitly states what the skill covers, when to use it, and supplies natural trigger phrases. The only weakness is a couple of trigger phrases that omit the canvas qualifier, creating slight conflict risk with generic documentation skills.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete capability areas — "Author and manage user-facing documentation", "writing style, tone, product screenshots, demo state preparation, and content structure for pages under docs/editor/" — with no vague filler, comprehensively covering what the skill does.	5 / 5
Completeness	Both questions are answered explicitly: the what is "Author and manage user-facing documentation for the Grida Canvas editor" and the when is "Use when creating or editing canvas editor documentation, capturing screenshots of canvas features, or planning visual demos" with concrete trigger phrases appended.	5 / 5
Trigger Term Quality	Explicit natural trigger phrases are given: "write user docs", "document this feature", "screenshot for docs", "canvas user guide", "update help page", plus synonyms in the when-clause ("creating or editing canvas editor documentation", "capturing screenshots", "planning visual demos"). Coverage of natural phrasings is comprehensive.	5 / 5
Distinctiveness Conflict Risk	The niche is clear (Grida Canvas editor, docs/editor/) and the body even scopes out "docs/wg/, docs/reference/", but the frontmatter trigger phrases "write user docs" and "update help page" lack a canvas qualifier, leaving minor overlap risk with other documentation skills. Not the anchor-5 case because a couple of triggers could fire for non-canvas docs requests; clearly above anchor 3 since the domain is otherwise sharply bounded.	4 / 5
	Total	19 / 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: .agents/skills/docs-canvas/SKILL.md
Commit: d086528

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