CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 tight, highly actionable body that assumes Claude's competence and gives concrete commands, templates, and specs. The only minor gap is the absence of an explicit validation feedback loop in the screenshot/publish workflow.

Suggestions

Add an explicit feedback loop to the Pre-Publish Checklist, e.g., 'If the page fails to render, fix frontmatter/MDX errors and re-run pnpm --filter docs start before publishing.'

Clarify that the demo-state list (fixture → scripting → URL params → manual) is a priority/precedence order rather than a sequential workflow, to avoid misreading it as steps to perform in turn.

DimensionReasoningScore

Conciseness

Lean and well-structured: tables for specs, tight bullets, and no over-explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Provides copy-paste-ready guidance — build commands ('turbo build --filter=editor && turbo start --filter=editor'), a frontmatter/page-structure template, concrete screenshot specs (960x960 WebP q90), and named scripting surfaces (globalThis.grida, WindowGlobalCurrentEditorProvider).

5 / 5

Workflow Clarity

Clear sequencing in the demo-state priority list and a Pre-Publish Checklist that includes a render verification step ('pnpm --filter docs start'), but no explicit validate→fix→retry feedback loop for the capture/publish flow.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections with one-level-deep, well-signaled deferrals (e.g., 'use the docs-svg-kit skill' for SVG figures and 'See docs/AGENTS.md' for linking rules); no nested reference chains.

5 / 5

Total

19

/

20

Passed

Description

100%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, well-scoped description that clearly states what the skill does, when to invoke it, and supplies natural trigger phrases. It is concise yet comprehensive and uses correct third-person voice.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Author and manage user-facing documentation', 'Covers writing style, tone, product screenshots, demo state preparation, and content structure' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (author/manage canvas editor docs covering style, screenshots, demo state, structure) and 'when' ('Use when creating or editing canvas editor documentation, capturing screenshots... or planning visual demos') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides explicit, natural trigger phrases users would actually say: 'write user docs', 'document this feature', 'screenshot for docs', 'canvas user guide', 'update help page'.

5 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche — the Grida Canvas editor under docs/editor/ — with domain-specific triggers, making conflict with other documentation skills minimal.

5 / 5

Total

20

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
gridaco/grida
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.