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.
94
Quality
47%
Does it follow best practices?
Impact
99%
1.76xAverage score across 10 eval scenarios
Pending
The risk profile of this skill
Optimize this skill with Tessl
npx tessl skill review --optimize ./claude/skills/canvas-design/SKILL.mdQuality
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 covers when to use the skill with explicit trigger guidance, which is a strength. However, it lacks specificity in concrete actions and could benefit from more natural trigger terms users would actually say. The distinctiveness is moderate but could conflict with other design-related skills.
Suggestions
Add more specific concrete actions like 'generate layouts, compose typography, create color schemes, design graphics' to improve specificity
Expand trigger terms to include common variations users would say: 'graphic', 'illustration', 'banner', 'flyer', 'infographic', 'artwork', 'visual'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (visual art, .png/.pdf) and some actions (create poster, art, design), but lacks comprehensive specific actions like 'generate layouts', 'apply color palettes', or 'compose typography'. The phrase 'beautiful visual art' is somewhat vague. | 2 / 3 |
Completeness | Clearly answers both what ('Create beautiful 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 using 'You should use this skill when...' clause. | 3 / 3 |
Trigger Term Quality | Includes some natural keywords users would say ('poster', 'piece of art', 'design', 'static piece'), but missing common variations like 'graphic', 'illustration', 'banner', 'flyer', 'infographic', or 'visual content'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to visual art creation with file format mentions (.png, .pdf), but 'design' is broad and could overlap with UI design, presentation design, or document formatting skills. The 'static piece' qualifier helps but isn't strongly distinctive. | 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 philosophical rather than technically actionable. While it provides creative direction and examples for design philosophy creation, it lacks concrete implementation details for actually generating PDF/PNG files. The content would benefit significantly from being condensed and restructured with clear tool usage instructions and validation steps.
Suggestions
Reduce content by 60-70% by removing repetitive emphasis on 'craftsmanship' and 'masterpiece' - state these principles once clearly instead of throughout
Add concrete, executable code examples for PDF/PNG generation using specific libraries (e.g., reportlab, PIL/Pillow, or cairo)
Split into SKILL.md overview with references to separate files: PHILOSOPHY_EXAMPLES.md, CANVAS_TECHNIQUES.md, and FONTS.md
Add explicit validation steps: 'Verify file was created: check output path exists', 'Validate dimensions match requirements', etc.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive repetition of concepts like 'craftsmanship' and 'masterpiece' throughout. Contains philosophical padding and redundant explanations that Claude doesn't need (e.g., explaining what a design philosophy is multiple times, repeating the same principles in different sections). | 1 / 3 |
Actionability | Provides a clear two-step process and includes concrete examples of philosophy names and descriptions. However, lacks executable code for PDF/PNG generation, specific tool commands, or technical implementation details for actually creating the visual outputs. | 2 / 3 |
Workflow Clarity | Has a clear two-step sequence (philosophy creation → canvas creation) with a refinement pass. However, lacks validation checkpoints, specific tool usage instructions, and concrete verification steps for ensuring output quality or file generation success. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files for detailed guidance. All content is inline despite being lengthy. The font directory reference (`./canvas-fonts`) is mentioned but not structured as proper progressive disclosure with clear navigation. | 1 / 3 |
Total | 6 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
b1b2fe0
Table of Contents
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.