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.
93
39%
Does it follow best practices?
Impact
98%
1.75xAverage score across 10 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/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 communicates both what the skill does and when to use it, earning good marks on completeness. 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 second-person voice ('You should use this skill') should be penalized per the rubric guidelines, though the rest uses appropriate framing.
Suggestions
Replace vague phrases like 'using design philosophy' and 'beautiful visual art' with specific capabilities such as 'generate posters, illustrations, infographics, banners, and graphic designs'.
Expand trigger terms to include common user phrases like 'illustration', 'graphic', 'infographic', 'flyer', 'banner', 'visual artwork', and 'image creation'.
Rewrite in third person voice (e.g., 'Creates original visual designs...' instead of 'You should use this skill when...') to align with style guidelines.
| 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
12%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a creative manifesto than actionable technical guidance. It is extremely verbose and repetitive, particularly around the themes of craftsmanship and visual minimalism, while ironically failing to practice the minimalism it preaches. The most critical gap is the complete absence of executable code or concrete technical instructions for actually generating PDF/PNG output files, which is the skill's stated purpose.
Suggestions
Add concrete, executable code examples showing how to generate PDF and PNG files (e.g., using reportlab, Pillow, or cairo), including font loading from `./canvas-fonts`.
Reduce repetition dramatically — the 'expert craftsmanship' and 'minimal text' directives are each stated 5+ times; state each principle once clearly.
Split the philosophy examples and canvas creation guidelines into separate reference files to improve progressive disclosure and reduce the main file's length.
Add validation checkpoints to the workflow, such as verifying the output file renders correctly, checking that text doesn't overlap, and confirming canvas dimensions before final output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and repetitive. The instruction to emphasize 'expert craftsmanship' is itself repeated at least 5-6 times across the document. Concepts like 'minimal text,' 'visual expression,' and 'masterpiece quality' are restated in nearly every section. The document is ~200+ lines when the core actionable content could be conveyed in ~50. It also explains abstract creative concepts at length rather than providing concrete technical guidance. | 1 / 3 |
Actionability | Despite its length, the skill provides almost no concrete, executable guidance. There are no code examples for generating PDFs or PNGs, no specific library usage, no commands, no file format details. Instructions like 'create museum quality work' and 'push aesthetics to the frontier' are aspirational but not actionable. The reference to `./canvas-fonts` directory is the only concrete path mentioned, but no code shows how to use it. | 1 / 3 |
Workflow Clarity | There is a discernible multi-step sequence: (1) create design philosophy as .md, (2) deduce subtle reference, (3) create canvas as .pdf/.png, (4) refine/polish. However, there are no validation checkpoints, no error recovery steps, and no concrete verification that outputs are correct. The 'final step' refinement pass is described philosophically rather than procedurally. | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of text with no references to supporting files. There are no bundle files, yet the content is long enough that sections like philosophy examples, canvas creation guidelines, and multi-page options could be split into separate reference documents. The `./canvas-fonts` directory is mentioned but never documented. | 1 / 3 |
Total | 5 / 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.
- Repository
- duclm1x1/Dive-Ai
- Commit
20ba150
- Reviewed
Table of Contents
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.