canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

1.76x

Quality

47%

Does it follow best practices?

Impact

99%

1.76x

Average score across 10 eval scenarios

Securityby

Failed to scan

The risk profile of this skill

Optimize this skill with Tessl

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

Quality

Discovery

67%

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 adequately communicates both what the skill does and when to use it, which is its strongest aspect. However, it suffers from somewhat vague language ('design philosophy', 'beautiful visual art') and could benefit from more specific capability listing and broader trigger term coverage. The copyright disclaimer, while responsible, doesn't aid in skill selection.

Suggestions

Expand trigger terms to include common variations like 'illustration', 'graphic', 'infographic', 'flyer', 'banner', 'wallpaper', or 'visual artwork'.

Replace vague phrases like 'using design philosophy' and 'beautiful visual art' with specific capabilities such as 'compose layouts with typography, shapes, color palettes, and illustrations'.

Use third person voice consistently — change 'You should use this skill when' to 'Use when' to align with the expected format and remove the second-person address.

Dimension	Reasoning	Score
Specificity	Names the domain (visual art/design) and some actions (create posters, art, designs), but 'using design philosophy' is vague and the specific capabilities like file format handling aren't well elaborated beyond mentioning .png and .pdf.	2 / 3
Completeness	Clearly answers both 'what' (create visual art in .png and .pdf documents) and 'when' ('when the user asks to create a poster, piece of art, design, or other static piece'), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes some natural trigger terms like 'poster', 'piece of art', 'design', and file formats '.png' and '.pdf', but misses common variations users might say such as 'illustration', 'graphic', 'infographic', 'flyer', 'banner', 'visual', or 'artwork'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'static piece' and visual art helps distinguish it from general document creation, but 'design' is broad and could overlap with UI design, web design, or presentation skills. The .pdf output could also conflict with PDF-focused skills.	2 / 3
	Total	9 / 12 Passed

Implementation

27%

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

This skill is highly verbose and repetitive, spending significant token budget on motivational language ('masterpiece,' 'museum quality,' 'expert craftsmanship') rather than actionable technical guidance. While the two-phase workflow concept is sound and the philosophy examples are useful, the skill lacks concrete implementation details (no code, no specific tools, no canvas dimensions) and could be dramatically condensed. The monolithic structure with no external references compounds the token efficiency problem.

Suggestions

Cut repetitive motivational language (craftsmanship emphasis, museum quality, etc.) to a single concise statement and reduce overall length by ~60%.

Add concrete, executable code examples showing how to generate PDF/PNG output (e.g., using reportlab, Pillow, or cairo), including canvas dimensions and font loading from ./canvas-fonts.

Split philosophy examples and canvas creation details into separate reference files (e.g., PHILOSOPHY_EXAMPLES.md, CANVAS_GUIDE.md) and link from the main skill.

Add explicit validation checkpoints: e.g., verify font files exist before rendering, check output dimensions, verify no elements exceed canvas bounds programmatically.

Dimension	Reasoning	Score
Conciseness	Extremely verbose and repetitive. The instruction to emphasize 'expert craftsmanship' is itself repeated at least 5-6 times across different sections. Concepts like 'minimal text,' 'visual expression,' and 'museum quality' are restated redundantly throughout. The skill could be condensed to roughly 1/3 its length without losing any actionable information.	1 / 3
Actionability	Provides some concrete guidance (philosophy examples, structural approach, font directory reference), but lacks executable code or specific tool commands for generating PDFs/PNGs. The canvas creation section is largely aspirational prose rather than concrete steps—there's no code showing how to actually render the output, what libraries to use, or what canvas dimensions to target.	2 / 3
Workflow Clarity	The two-step workflow (philosophy creation → canvas creation) is clearly identified, and there's a refinement pass at the end. However, there are no validation checkpoints, no error recovery steps, and the 'deducing the subtle reference' step is vaguely defined. The final refinement step lacks concrete criteria for what 'pristine' means in practice.	2 / 3
Progressive Disclosure	The entire skill is a monolithic wall of text with no references to external files for detailed guidance. The philosophy examples, canvas creation instructions, multi-page options, and refinement steps are all inline. Content like the philosophy examples and the detailed canvas creation guidelines could easily be split into separate reference files.	1 / 3
	Total	6 / 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: einverne/dotfiles
Commit: b1b2fe0

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