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.

Quality

44%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Content

22%

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

This skill is essentially a skeleton that delegates all meaningful content to sub-skill files that don't exist in the bundle. It lacks any concrete, actionable guidance for producing .png or .pdf output—no code, no tool references, no library usage, no examples. The two-step workflow is stated at a very high level but the critical second step (actual visual creation) has zero implementation detail.

Suggestions

Add concrete, executable code examples showing how to generate .png and .pdf files (e.g., using Python libraries like Pillow, reportlab, or cairo, or using HTML-to-image conversion).

Flesh out the workflow for step 2 with specific tool invocations, validation steps (e.g., verify output file exists and is valid), and error recovery guidance.

Include at least one complete end-to-end example: a sample philosophy → the specific code/commands that produce a visual output file.

Either include the sub-skill files in the bundle or inline the essential content so the skill is self-contained enough to be actionable on its own.

Dimension	Reasoning	Score
Conciseness	Reasonably brief but includes some unnecessary framing ('These are instructions for creating design philosophies') and the emoji/branding ('Fractal Skills') adds no value. The phrase 'aesthetic movements that are then EXPRESSED VISUALLY' is somewhat redundant given the context.	2 / 3
Actionability	The skill provides no concrete code, commands, or executable examples for generating .png or .pdf files. It describes a conceptual process ('create a VISUAL PHILOSOPHY') but gives no specific tools, libraries, or code snippets Claude should use to actually produce visual output.	1 / 3
Workflow Clarity	While two high-level steps are listed (philosophy creation then canvas expression), the actual process for step 2 is entirely absent—there are no instructions for how to generate the .pdf or .png, no tool usage, no validation, and no error handling. The workflow is incomplete.	1 / 3
Progressive Disclosure	The skill references four sub-skill files with clear one-level-deep links, which is good structure. However, no bundle files were provided, so the references lead nowhere, and the SKILL.md itself contains almost no substantive content—it's essentially just a table of contents with no quick-start or overview content to stand on its own.	2 / 3
	Total	6 / 12 Passed

Description

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 relies on somewhat vague language ('beautiful visual art', 'design philosophy') rather than listing concrete capabilities, and its trigger term coverage could be broader to capture more user phrasings. The copyright disclaimer, while responsible, doesn't aid in skill selection.

Suggestions

List more specific concrete actions such as 'create posters, illustrations, infographics, banners, and abstract art' to improve specificity and trigger term coverage.

Expand trigger terms to include common user phrasings like 'illustration', 'graphic', 'infographic', 'flyer', 'banner', 'wall art', or 'visual artwork'.

Replace vague phrases like 'design philosophy' and 'beautiful visual art' with concrete descriptions of what the skill actually produces or the techniques it uses.

Dimension	Reasoning	Score
Specificity	Names the domain (visual art, design) and some actions (create poster, piece of art, design), but 'beautiful visual art' and 'design philosophy' are vague. It doesn't list multiple concrete specific actions like layout techniques, color palettes, typography, etc.	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'). The explicit 'Use when' equivalent clause is present.	3 / 3
Trigger Term Quality	Includes some natural trigger terms like 'poster', 'piece of art', 'design', '.png', '.pdf', and 'static piece', but misses common variations users might say such as 'illustration', 'graphic', 'infographic', 'flyer', 'banner', 'visual', or 'artwork'.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to visual art/design creation, but 'design' is broad and could overlap with UI design, web design, or presentation skills. The '.png and .pdf' output formats and 'static piece' help narrow it, but 'design philosophy' is vague and could cause confusion.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 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

Repository: Dokhacgiakhoa/antigravity-ide
Commit: c4a059b

Reviewed: 5 days 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.