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

44%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/canvas-design/SKILL.md

Quality

Content

35%Weight 40%Scale 1-5

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

The skill lays out a clear multi-phase creative workflow but is heavily padded with repeated emphasis, offers little concrete execution guidance, and inlines material that would be better split into reference files. Its one bundle reference points to a non-existent directory.

Suggestions

Collapse the repeated craftsmanship/minimal-text emphasis into a single stated principle; remove redundant restatements to respect the context budget.

Add concrete, executable guidance for rendering output (e.g. a named PDF/PNG generation approach or script) instead of purely aesthetic directives.

Move the five philosophy examples into a separate references file and verify the ./canvas-fonts directory actually exists, or remove the dangling reference.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose with repeated padded sections—craftsmanship phrases ('meticulously crafted', 'painstaking attention', 'master-level execution') and 'minimal text / EXPRESSED VISUALLY' are restated many times rather than stated once.	2 / 5
Actionability	Guidance is mostly high-level and philosophical ('create a masterpiece', 'push aesthetics to the frontier') with only a few concrete constraints (file types, single page, margins); it gives no executable tooling or rendering steps for producing the PDF/PNG.	2 / 5
Workflow Clarity	Steps are sequenced via clear headers (philosophy -> deduce reference -> canvas -> final refinement), but validation checkpoints are only implicit ('Check carefully that all text... have breathing room') with no real feedback loop.	3 / 5
Progressive Disclosure	Section headers provide some structure, but all content—including five full philosophy examples—is inlined in SKILL.md, and the only referenced bundle path (./canvas-fonts) does not exist in the skill directory.	3 / 5
	Total	10 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 conveys a clear 'what' (creating visually-expressed design philosophies with specific output file types) but omits any 'when to use it' trigger guidance. It is reasonably distinct but lacks natural trigger terms and explicit invocation cues.

Suggestions

Add an explicit 'Use when ...' clause naming concrete triggers (e.g. 'Use when creating visual design philosophies, aesthetic movements, or art-directed single-page posters/PDFs').

Replace abstract phrasing like 'EXPRESSED VISUALLY' with concrete capability verbs and include file extensions as trigger terms (.md, .pdf, .png).

Tighten the description to one concise sentence covering both what and when, matching the good-example style.

Dimension	Reasoning	Score
Specificity	Names the domain ('design philosophies', 'aesthetic movements') and a couple of concrete actions ('creating', 'EXPRESSED VISUALLY', outputting .md/.pdf/.png), but the actions remain largely abstract rather than comprehensive.	3 / 5
Completeness	It states clearly what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes some relevant natural terms ('design philosophies', 'aesthetic movements') but misses common variations or synonyms a user would naturally say, and offers no explicit trigger phrases.	3 / 5
Distinctiveness Conflict Risk	The visual-design-philosophy niche is mostly distinct from other skills, with only minor overlap risk against general design or document-generation skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/canvas-design/SKILL.md
Commit: 1f67c44

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