Name: docs-canvas
Rating: 64 (1 reviews)
Author: cursor

docs-canvas

Render a documentation-style Cursor Canvas that organizes architecture notes, API references, walkthroughs, and how-tos into a navigable layout with sections, tables of contents, and cross-references. Use when the user asks for a docs canvas, documentation overview, architecture walkthrough, API reference page, or wants to render structured documentation as an interactive canvas.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./docs-canvas/skills/docs-canvas/SKILL.md

Quality

Content

61%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 is a well-structured but explicitly placeholder outline that defers most concrete policy to an external SKILL.md. It scores well on conciseness and structure but lacks executable guidance and validation checkpoints in its workflow.

Suggestions

Add at least one concrete, copy-paste-ready component example (e.g., a section or TOC snippet) so the 'Render with canvas primitives' guidance is executable rather than abstract.

Insert a validation/self-check checkpoint into the workflow (e.g., verify the canvas renders and cross-references resolve before finishing), since the skill references a self-check policy upstream.

Replace the placeholder status banner with a concise note once the body is written, or fold the deferred policy pointers into a single clearly labeled 'See canvas/SKILL.md for...' reference line.

Dimension	Reasoning	Score
Conciseness	The body is a lean outline with no padded explanations of concepts Claude already knows; each section earns its place, though as an explicit placeholder it is sparser than a finished skill body.	4 / 5
Actionability	Guidance is structural and high-level ('Use cards/sections', 'Use diagrams (DAG layout, mermaid)', 'Use callouts') with no concrete executable code or specific commands, leaving key execution details implied.	3 / 5
Workflow Clarity	A rough sequence exists (Gather -> Plan -> Render -> Tone -> Be creative) but there are no validation or verification checkpoints for the generation workflow.	3 / 5
Progressive Disclosure	Well-organized sections with clearly signaled one-level-deep references to the canvas SKILL.md and SDK .d.ts files; no bundle files exist to verify, and the structure is appropriate for an under-50-line outline.	4 / 5
	Total	14 / 20 Passed

Description

88%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 is strong: it states concrete capabilities and provides explicit, natural trigger phrases covering both 'what' and 'when'. Minor room to add format/extension variants for trigger-term completeness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'organizes architecture notes, API references, walkthroughs, and how-tos into a navigable layout with sections, tables of contents, and cross-references' — giving comprehensive coverage of capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (render a docs canvas that organizes documentation) and 'when' via a concrete 'Use when the user asks for...' clause with multiple trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user-facing phrases ('docs canvas, documentation overview, architecture walkthrough, API reference page, render structured documentation as an interactive canvas') with good synonym coverage, but lacks file-extension or format variants.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche ('Cursor Canvas', 'docs canvas') with distinct triggers, though it could overlap slightly with generic documentation or canvas skills.	4 / 5
	Total	18 / 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: cursor/plugins
Path: docs-canvas/skills/docs-canvas/SKILL.md
Commit: 51a96e0

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