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.
Install with Tessl CLI
npx tessl i github:Dokhacgiakhoa/antigravity-ide --skill canvas-designOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 both what the skill does and when to use it, which is its main strength. However, it lacks specificity in concrete actions and could benefit from more comprehensive trigger terms. The phrase 'design philosophy' is vague fluff that doesn't add value.
Suggestions
Add more specific concrete actions like 'generate layouts, compose graphics, apply color schemes, create typography arrangements'
Expand trigger terms to include common variations: 'graphic, illustration, banner, flyer, infographic, artwork, visual design'
Remove vague phrase 'using design philosophy' and replace with specific techniques or capabilities
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (visual art, .png/.pdf) and some actions (create poster, piece of art, design), but lacks comprehensive specific actions like 'generate layouts', 'apply color palettes', or 'compose typography'. | 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. | 3 / 3 |
Trigger Term Quality | Includes some natural terms users would say ('poster', 'piece of art', 'design') but missing common variations like 'graphic', 'illustration', 'banner', 'flyer', 'infographic', or 'visual'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to visual art creation but could overlap with other design-related skills; the mention of 'design' is broad and '.pdf documents' could conflict with PDF manipulation skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides good structural organization with clear references to sub-skills, but the main content is too abstract to be actionable. It describes what to create (visual philosophy, .pdf/.png files) without providing any concrete implementation details, code examples, or tool-specific commands for actually generating the output files.
Suggestions
Add concrete code examples showing how to generate .pdf and .png files (e.g., using Python libraries like PIL, reportlab, or cairo)
Include at least one complete executable example that takes a design philosophy and produces an actual output file
Add validation steps to verify generated files are valid and meet quality criteria
Replace abstract instructions like 'Express by creating it on a canvas' with specific tool commands and parameters
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Reasonably brief but includes some unnecessary framing ('These are instructions for...') and the emoji/formatting adds visual noise without adding clarity. The core content is lean but could be tighter. | 2 / 3 |
Actionability | Extremely vague - no concrete code, commands, or executable examples. 'Create a VISUAL PHILOSOPHY' and 'Express by creating it on a canvas' are abstract directions without any specific implementation guidance for generating .pdf or .png files. | 1 / 3 |
Workflow Clarity | Two-step process is outlined (philosophy creation then expression), but lacks any validation checkpoints, specific tools/commands for file generation, or error handling. The actual 'how' is entirely delegated to sub-skills. | 2 / 3 |
Progressive Disclosure | Good structure with clear overview and well-signaled one-level-deep references to sub-skills. The four knowledge modules are clearly labeled and linked, making navigation straightforward. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
91%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.