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

67%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs-canvas/skills/docs-canvas/SKILL.md

Quality

Content

35%

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

This skill is self-described as a placeholder and it shows — it provides a reasonable structural outline for a docs canvas but lacks any concrete, executable guidance. There are no code examples, no component usage patterns, no specific prop shapes, and no validation steps. It reads as a planning document rather than an actionable skill.

Suggestions

Add at least one complete, executable example showing how to build a minimal docs canvas using the actual SDK components and props from the referenced .d.ts files.

Replace vague directives like 'Use cards/sections' and 'Use diagrams' with specific component names, prop examples, and rendered output patterns.

Add a validation or self-check step (e.g., verify the canvas renders, check that TOC links resolve) to establish a feedback loop in the workflow.

Remove or consolidate the 'Tone and content' and 'Be creative' sections into a brief set of concrete guidelines rather than abstract encouragement.

Dimension	Reasoning	Score
Conciseness	The skill explicitly labels itself as a placeholder, which means much of the content is aspirational rather than functional. Some sections like 'Tone and content' and 'Be creative' are vague filler that don't add actionable value. However, it's not excessively verbose or explaining things Claude already knows.	2 / 3
Actionability	The skill provides no concrete code, no executable examples, no specific component names or prop usage, and no copy-paste ready snippets. It reads as a high-level outline with vague directives like 'Use cards/sections to group related content visually' without showing how.	1 / 3
Workflow Clarity	There is a rough sequence (gather → plan → render), but steps lack specificity and there are no validation checkpoints, no error handling guidance, and no feedback loops. The workflow is more of a conceptual outline than an actionable process.	2 / 3
Progressive Disclosure	The skill references external files (SKILL.md, index.d.ts) for the SDK and generation policy, which is good progressive disclosure. However, no bundle files are provided to verify these references, and the skill itself doesn't clearly separate overview from detailed content since it's all at one shallow level.	2 / 3
	Total	7 / 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.

This is a strong skill description that clearly articulates specific capabilities, provides explicit trigger guidance via a 'Use when...' clause, and uses natural language terms users would employ. It effectively distinguishes itself through the combination of documentation content types and the Cursor Canvas rendering format, making it easy for Claude to select appropriately.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: organizing architecture notes, API references, walkthroughs, and how-tos into a navigable layout with sections, tables of contents, and cross-references. These are concrete, well-defined capabilities.	3 / 3
Completeness	Clearly answers both 'what' (render documentation-style Cursor Canvas with architecture notes, API references, walkthroughs, how-tos, TOC, cross-references) and 'when' (explicit 'Use when...' clause listing specific trigger scenarios).	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'docs canvas', 'documentation overview', 'architecture walkthrough', 'API reference page', 'structured documentation', 'interactive canvas'. Good coverage of variations a user might naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: documentation-style Cursor Canvas. The combination of 'Cursor Canvas' format with documentation-specific content types (architecture notes, API references) creates a well-defined scope unlikely to conflict with generic documentation or generic canvas skills.	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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: cursor/plugins
Commit: cfd81b3

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