Name: docs-canvas
Rating: 70.39999999999999 (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

86%

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

Quality

Content

72%

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

A clean, well-structured outline that respects token budget and organizes content well, but it is explicitly a placeholder: actionability and workflow clarity are capped at 2 because there is no executable code, no concrete examples, and no validation checkpoints, and the skill body is still to be written.

Suggestions

Replace the placeholder outline with concrete, executable guidance: add a minimal runnable canvas component example and real prop shapes from the referenced .d.ts files so the 'Render with canvas primitives' section is copy-paste ready.

Add an explicit validation/checkpoint step to the workflow (e.g., verify the canvas renders and cross-references resolve before declaring done) to lift workflow clarity toward 3.

Once the body is written, remove the 'Status: placeholder' banner so the skill reads as finished guidance rather than a starting outline.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding — "Accept any of: a directory of markdown files, a single doc URL, an inline outline, or a question" assumes Claude's competence and never explains basic concepts, matching the score-3 lean-and-efficient anchor.	3 / 3
Actionability	Quotes "Use cards/sections", "Use code blocks with syntax highlighting", and "Use diagrams (DAG layout, mermaid)" name concrete primitives but give no executable code or copy-paste examples; the body openly flags itself as a placeholder ("the full skill body still needs to be written"), so it lands at the score-2 "some concrete guidance but incomplete" anchor rather than the score-3 fully-executable anchor.	2 / 3
Workflow Clarity	A clear sequence exists (Gather → Plan layout → Render → Tone → Be creative) with a numbered plan list, but there are no explicit validation checkpoints and the body is self-declared as an unfinished outline ("Treat the steps below as a starting outline and refine"), matching the score-2 "steps listed but checkpoints missing" anchor rather than the score-3 explicit-validation anchor.	2 / 3
Progressive Disclosure	No bundle files exist (no references/scripts/assets directories) and the under-50-line single-purpose body is organized into well-signaled sections pointing one level out to canvas prerequisites, so per the simple-skills scoring note it meets the score-3 well-organized-sections anchor.	3 / 3
	Total	10 / 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.

A strong, well-formed description: it states a concrete capability, supplies explicit and natural trigger phrases, answers both what and when, and occupies a distinct niche. No changes needed.

Dimension	Reasoning	Score
Specificity	Quotes "Render a documentation-style Cursor Canvas" and "organizes architecture notes, API references, walkthroughs, and how-tos into a navigable layout with sections, tables of contents, and cross-references" — a comprehensive set of concrete actions, matching the score-3 anchor rather than the score-2 "some actions" anchor.	3 / 3
Completeness	The description answers "what" (render a docs canvas organizing documentation into a navigable layout) and "when" via an explicit "Use when the user asks for a docs canvas..." clause, matching the score-3 both-what-and-when anchor; not score 2 because the trigger is explicit, not merely implied.	3 / 3
Trigger Term Quality	Quotes "docs canvas, documentation overview, architecture walkthrough, API reference page" and "render structured documentation as an interactive canvas" — natural phrases a user would say, matching the score-3 good-coverage anchor over the score-2 "some relevant keywords" anchor.	3 / 3
Distinctiveness Conflict Risk	The Cursor Canvas docs niche with distinct triggers ("docs canvas", "render structured documentation as an interactive canvas") carves a clear niche unlikely to trigger the wrong skill, matching the score-3 clear-niche anchor.	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: cursor/plugins
Path: docs-canvas/skills/docs-canvas/SKILL.md
Commit: fe77e77

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.