canvas-design

These are instructions for creating design philosophies - aesthetic movements that are then EXPRESSED VISUALLY. Output only .md files, .pdf files, and .png files.

Quality

22%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Failed to scan

The risk profile of this skill

Optimize this skill with Tessl

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

Quality

Discovery

17%

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 is too vague and abstract to effectively guide skill selection. It lacks concrete actions, natural trigger terms users would use, and an explicit 'Use when...' clause. The mention of specific output formats (.md, .pdf, .png) is a minor positive but insufficient to compensate for the overall lack of clarity and completeness.

Suggestions

Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a design philosophy, visual aesthetic, art movement, style guide, or mood board.'

Replace vague language with specific concrete actions, e.g., 'Generates design philosophy documents with visual expressions including mood boards, color palettes, typography selections, and style reference images.'

Include common user-facing keywords like 'design style', 'visual identity', 'aesthetic', 'mood board', 'art direction' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ('design philosophies', 'aesthetic movements') and mentions output formats (.md, .pdf, .png), but the core action is vague—'creating design philosophies' and 'expressed visually' don't describe concrete, specific actions like 'generate mood boards' or 'produce style guides'.	2 / 3
Completeness	The description partially addresses 'what' (creating design philosophies expressed visually) but has no 'Use when...' clause or equivalent trigger guidance, and the 'what' itself is vague. Per the rubric, a missing 'Use when' clause caps completeness at 2, and the weak 'what' brings it to 1.	1 / 3
Trigger Term Quality	The description lacks natural keywords a user would say. Terms like 'design philosophies' and 'aesthetic movements' are niche and unlikely to match typical user queries. Common trigger terms like 'design style', 'visual aesthetic', 'mood board', or 'art movement' are absent.	1 / 3
Distinctiveness Conflict Risk	The concept of 'design philosophies as aesthetic movements expressed visually' is somewhat niche, which helps distinctiveness, but the vague phrasing could overlap with general design, art, or visual creation skills.	2 / 3
	Total	6 / 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 repetitive, restating the same principles (craftsmanship, minimalism, visual expression) many times without adding new information. While it provides a clear creative framework with useful philosophy examples, it lacks technical actionability—there are no executable code snippets, specific tool commands, or library references for actually producing PDF/PNG outputs. The content would benefit significantly from aggressive editing and splitting into separate reference files.

Suggestions

Cut repetitive emphasis on craftsmanship, minimalism, and visual expression to single authoritative statements—the same points are made 4-6 times each across different sections.

Add concrete, executable code examples showing how to actually generate PDF/PNG files (e.g., using specific Python libraries like reportlab, PIL/Pillow, or cairo), including font loading from the referenced `./canvas-fonts` directory.

Split the philosophy examples and canvas creation detailed instructions into separate reference files (e.g., PHILOSOPHY_EXAMPLES.md, CANVAS_GUIDE.md) and link to them from a concise overview.

Add explicit validation checkpoints in the canvas creation workflow, such as checking canvas dimensions, verifying no elements overlap boundaries, and confirming font availability before rendering.

Dimension	Reasoning	Score
Conciseness	Extremely verbose and repetitive. The instruction to emphasize 'expert craftsmanship' is itself repeated at least 5-6 times across different sections. Concepts like 'minimal text,' 'visual expression,' and 'museum quality' are restated redundantly throughout. The skill could be cut by 60%+ without losing actionable content.	1 / 3
Actionability	Provides some concrete guidance through philosophy examples and a structured two-step process, but lacks executable code, specific tool commands, or concrete technical instructions for actually generating PDFs/PNGs. References a `./canvas-fonts` directory but gives no code for rendering, no library usage, and no specific commands for file creation.	2 / 3
Workflow Clarity	The two-step workflow (philosophy creation → canvas creation) is clearly sequenced, and there's a refinement pass at the end. However, there are no validation checkpoints, no error recovery steps, and the 'final step' refinement lacks concrete criteria for what 'pristine' means. The destructive/iterative nature of the refinement step has no feedback loop.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files for detailed guidance. The philosophy examples, canvas creation instructions, multi-page options, and refinement steps are all inline in one massive document. Content like the philosophy examples or canvas creation details could be split into separate reference files.	1 / 3
	Total	6 / 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: sickn33/antigravity-awesome-skills
Commit: e18e63c

Reviewed: 4 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.