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

31%

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 ./plugins/AI-Agents-Safe-Coding-Skills/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 body is a verbose, monolithic aesthetic brief: it sequences the work clearly enough but offers almost no executable guidance for actually generating PDF/PNG output, repeats craftsmanship refrains excessively, and references a './canvas-fonts' directory that is not present in the bundle. It reads as creative direction rather than a concrete, actionable skill.

Suggestions

Provide concrete, executable guidance for producing output — name a tool/library (e.g. reportlab, Pillow, or HTML-to-PDF) with a minimal copy-paste example for rendering the canvas.

Trim the repeated craftsmanship rhetoric to a single concise statement and remove filler lines to reduce token bloat.

Add an explicit validation/refinement checkpoint (e.g. 'verify nothing overlaps and text stays within margins before outputting') and supply the missing ./canvas-fonts directory or remove the reference.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose with heavy repetition — 'EXPERT CRAFTSMANSHIP', 'meticulously crafted', and 'countless hours' are restated many times, and filler like 'Take a moment to gather thoughts and clear the mind' and 'This is true art' adds padding, matching the 'noticeably verbose; several unnecessary explanations or padded sections' anchor; it is not a 1 because the prose is aesthetic direction rather than explaining basics Claude already knows.	2 / 5
Actionability	Despite specifying output formats and pointing to './canvas-fonts', the body gives no executable mechanism for producing a .pdf/.png (no library, tool, or code) and resorts to vague directives like 'Get creative' and 'Go back to the code and refine' with no code present, fitting the 'minimal concrete guidance; high-level hints but missing the specific steps' anchor; it is not a 3 because no concrete executable steps or examples are provided.	2 / 5
Workflow Clarity	A rough sequence exists (create philosophy .md → deduce reference → render canvas → final refinement pass) and is sectioned, but there are no validation or verification checkpoints and the 'Final step' refinement loop has no feedback mechanism, matching the 'steps listed but validation gaps; checkpoints missing or implicit' anchor; it is not a 4 because explicit checkpoints are absent.	3 / 5
Progressive Disclosure	The body uses section headers for navigation and keeps references one level deep, but no bundle files exist (references/scripts/assets/canvas-fonts are all absent, making the './canvas-fonts' reference broken) and all philosophy examples and guidance are inlined in a single ~135-line file that could be split, matching the 'some structure but could be better organized' anchor; it is not a 2 because headers do provide reasonable structure.	3 / 5
	Total	10 / 20 Passed

Description

28%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 is vague and missing any usage trigger: it states an abstract creative purpose and output formats but no concrete actions or 'when to use' guidance. It is moderately distinct as a niche but weak on specificity, trigger terms, and completeness.

Suggestions

Rewrite the description in third person listing concrete actions, e.g. 'Generates a written design-philosophy manifesto (.md) and renders it as a visual art canvas (.pdf or .png).'

Add an explicit 'Use when...' trigger clause with natural user phrases such as 'create a design philosophy', 'make a poster or art canvas', or 'design an aesthetic movement'.

Include relevant file extensions and synonyms (.pdf, .png, poster, art print) to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain ('creating design philosophies - aesthetic movements that are then EXPRESSED VISUALLY') and the output formats (.md, .pdf, .png), but the only action stated is the generic 'creating'; there are no concrete enumerated actions, matching the 'names the domain but actions are minimal or generic' anchor rather than the level-3 anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It gives only a vague 'what' (creating design philosophies) and entirely lacks any 'when' / 'Use when...' trigger clause, which per the judging guidelines caps completeness at 3 and matches the 'has a vague what and no when' anchor; it is not a 3 because the 'what' is not clearly stated.	2 / 5
Trigger Term Quality	Phrases like 'design philosophies', 'aesthetic movements', and 'EXPRESSED VISUALLY' are art jargon rather than natural terms a user would say when needing this skill, and there are no everyday synonyms or trigger phrases, fitting the 'one or two generic keywords; missing the natural phrases users say' anchor; it is not a 1 because a couple of domain keywords are present.	2 / 5
Distinctiveness Conflict Risk	The art-movement / visual-philosophy niche plus the .md/.pdf/.png output restriction is fairly distinct, but the abstract phrasing could overlap with presentation or design-viz skills, matching the 'somewhat specific but could still overlap' anchor rather than the more distinct level-4 anchor.	3 / 5
	Total	9 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/canvas-design/SKILL.md
Commit: 57c135b

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