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

—

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 vague about what concrete actions the skill performs and entirely lacks a 'Use when...' clause to guide skill selection. While the domain of 'design philosophies' and 'aesthetic movements' provides some uniqueness, the absence of natural trigger terms and explicit trigger guidance makes it difficult for Claude to reliably select this skill from a pool of alternatives.

Suggestions

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

Replace vague language like 'expressed visually' with specific concrete actions, e.g., 'Generates design philosophy documents with mood boards, color palettes, typography selections, and visual examples.'

Include common user-facing keywords such as 'design style', 'visual identity', 'art direction', 'aesthetic guide', or 'style reference' 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 describe concrete steps like 'generate mood boards' or 'compile style guides'.	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, which per the rubric caps this at a maximum of 2, but 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 abstract; common trigger terms like 'design style', 'visual aesthetic', 'art movement', or 'style guide' are absent.	1 / 3
Distinctiveness Conflict Risk	The combination of 'design philosophies' and 'aesthetic movements' is somewhat distinctive, but the vague framing could overlap with general design, art, or visual creation skills. The output format constraint (.md, .pdf, .png) adds some distinction but isn't enough for a clear 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 excessively verbose with significant redundancy, particularly around craftsmanship emphasis and minimal-text principles that are restated in nearly every section. While the creative vision is clear and the two-step workflow is identifiable, the lack of executable code for PDF/PNG generation, absence of concrete validation steps, and monolithic structure significantly weaken its effectiveness as a skill file. The content reads more like an artistic manifesto than actionable instructions for Claude.

Suggestions

Reduce redundancy dramatically: consolidate the craftsmanship emphasis and minimal-text principles into single, authoritative statements rather than repeating them 5+ times across sections.

Add concrete, executable code examples for PDF/PNG generation (e.g., using reportlab, PIL/Pillow, or matplotlib) so Claude knows exactly which tools and APIs to use for canvas creation.

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

Add explicit validation checkpoints: define what 'pristine' means with measurable criteria (e.g., 'verify no elements overlap by checking bounding boxes,' 'confirm all text fits within margins with X px padding').

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~200+ lines with extensive repetition. The instruction to 'emphasize craftsmanship REPEATEDLY' leads to the same point being restated 5+ times. Concepts like 'minimal text' and 'visual expression' are repeated across multiple sections. Many paragraphs explain things Claude already understands (what a design philosophy is, what visual expression means). The philosophy examples, while useful, are overly numerous.	1 / 3
Actionability	Provides a clear two-step workflow (create philosophy .md, then create canvas .pdf/.png) with some concrete guidance like file formats and paragraph counts. However, the actual canvas creation lacks executable code or specific tool commands—it's mostly abstract direction ('push aesthetics to the frontier,' 'follow design instinct'). References to './canvas-fonts' directory and downloading fonts are concrete but lack specific commands. No code examples for PDF/PNG generation.	2 / 3
Workflow Clarity	The two-step workflow (philosophy creation → canvas creation) is identifiable, and there's a refinement pass at the end. However, validation checkpoints are weak—the 'FINAL STEP' refinement is vague ('take a second pass') without concrete validation criteria. The 'DEDUCING THE SUBTLE REFERENCE' step is ambiguously positioned between the two main steps. No explicit error recovery or verification steps for the visual output.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files despite the complexity warranting them. The philosophy examples could be in a separate EXAMPLES.md. The canvas creation guidelines, font instructions, and multi-page options could all be split out. No bundle files are provided or referenced (except './canvas-fonts' directory). Everything is crammed into one long document.	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: fb2efea

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.