CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

51%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Failed to scan

The risk profile of this skill

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/canvas-design/SKILL.md
SKILL.md
Quality
Evals
Security

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 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, and the copyright disclaimer, while important, doesn't help with skill selection.

Suggestions

Add more specific concrete actions like 'generate layouts, compose typography, create color schemes, design graphics'

Expand trigger terms to include common variations: 'graphic', 'illustration', 'banner', 'flyer', 'infographic', 'visual content'

Remove vague phrases like 'design philosophy' and the copyright disclaimer which don't aid skill selection

DimensionReasoningScore

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'.

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 '.pdf documents' could conflict with PDF manipulation skills, and 'design' is quite broad.

2 / 3

Total

9

/

12

Passed

Implementation

35%

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

This skill functions primarily as a navigation hub to sub-skills rather than providing actionable guidance itself. It lacks concrete implementation details—no code for generating PNGs/PDFs, no tool usage examples, no specific commands. The two-step workflow is too abstract to be useful without reading all four linked documents.

Suggestions

Add concrete code examples showing how to actually generate .png and .pdf files (e.g., using Python libraries like PIL, reportlab, or cairo)

Include at least one complete mini-example: input description → design philosophy snippet → output file creation command

Provide a brief summary of what each sub-skill contains so Claude can decide which to reference without reading all four

Add validation steps for the output files (e.g., verify file was created, check dimensions/format)

DimensionReasoningScore

Conciseness

Reasonably brief but includes some unnecessary framing ('These are instructions for...', 'undertake this task'). The emoji and 'Fractal Skills' label add no value. Could be tighter.

2 / 3

Actionability

No concrete code, commands, or executable examples. Describes what to create ('visual philosophy') but provides no actual implementation guidance—just abstract concepts and links to other files.

1 / 3

Workflow Clarity

Two-step process is mentioned (philosophy creation, then canvas expression) but lacks any detail on how to execute either step. No validation checkpoints or concrete sequence for the actual creation process.

2 / 3

Progressive Disclosure

References four sub-skill files which is good structure, but the main skill provides almost no standalone value—it's essentially just a table of contents with minimal overview content.

2 / 3

Total

7

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
Dokhacgiakhoa/antigravity-ide
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.