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 serve as an effective skill selector. It lacks concrete actions, natural trigger terms users would use, and any explicit 'Use when...' guidance. While the concept of design philosophies expressed visually is somewhat unique, the description doesn't provide enough detail for Claude to reliably choose this skill over others.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to create a design philosophy, visual aesthetic, art movement guide, or style manifesto.'

List specific concrete actions such as 'Generates written design philosophy documents, renders visual mood boards as PNG images, and produces PDF style guides with color palettes and typography samples.'

Include natural user-facing keywords like 'design style', 'visual aesthetic', 'mood board', 'art direction', 'style guide', or 'design manifesto' 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 actions are vague—'creating' and 'expressed visually' don't specify concrete steps like generating mood boards, writing style guides, or rendering visual examples.	2 / 3
Completeness	The 'what' is only partially addressed (creating design philosophies expressed visually), and there is no 'when' clause or explicit trigger guidance at all. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the weak 'what' brings it down 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 abstract; common trigger terms like 'design style', 'visual aesthetic', 'art movement', 'brand style', or 'mood board' are absent.	1 / 3
Distinctiveness Conflict Risk	The concept of 'design philosophies as aesthetic movements' is somewhat distinctive, but the vague framing could overlap with general design, branding, or image generation skills. The output format list (.md, .pdf, .png) adds some specificity but isn't enough to clearly carve out a niche.	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 a creative brief masquerading as a technical skill file. While it communicates a clear artistic vision and provides useful philosophy examples, it is extremely verbose with heavy repetition (especially around craftsmanship and minimalism), lacks any concrete technical instructions for PDF/PNG generation, and dumps all content into a single file. The irony of a skill about minimalism being maximally verbose undermines its effectiveness.

Suggestions

Cut content by 50-60%: remove repeated emphasis on craftsmanship, consolidate the 'minimal text' principle to one mention, and trim philosophy examples to 2-3 instead of 5.

Add concrete technical instructions: specify what tools/libraries to use for PDF/PNG generation, include executable code snippets or specific commands for canvas creation.

Split into multiple files: move philosophy examples to a PHILOSOPHY_EXAMPLES.md, canvas creation details to CANVAS_GUIDE.md, and keep SKILL.md as a concise overview with references.

Add validation checkpoints: include specific criteria for evaluating output quality (e.g., 'verify no overlapping elements', 'confirm all text within margins') as a concrete checklist rather than repeated exhortations.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~200+ lines with extensive repetition. The instruction to 'emphasize craftsmanship REPEATEDLY' leads to the same point being made 5+ times. Concepts like 'minimal text' and 'visual expression' are restated in nearly every section. Many paragraphs explain creative philosophy that Claude could infer from a much shorter prompt.	1 / 3
Actionability	The skill provides a clear two-step workflow and philosophy examples that give concrete direction, but lacks any executable code, specific tool commands, or technical instructions for actually generating PDFs/PNGs. References to './canvas-fonts' directory and 'code' for refinement suggest technical steps exist but are never specified.	2 / 3
Workflow Clarity	The two-phase workflow (philosophy creation → canvas creation) is clearly sequenced, and there is a refinement/second-pass step. However, there are no validation checkpoints, no error recovery steps, and the 'FINAL STEP' refinement lacks concrete criteria for what 'pristine' means. The process for actually generating visual output (PDF/PNG) is entirely unspecified technically.	2 / 3
Progressive Disclosure	Everything is in a single monolithic file with no references to supporting documents. The philosophy examples, canvas creation instructions, multi-page options, and refinement steps are all inline. With no bundle files provided, the reference to './canvas-fonts' is unresolvable, and content that could be split (e.g., philosophy examples, canvas creation details) is all crammed together.	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: 1930a07

Reviewed: about 2 hours 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.