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

51%

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-claude/skills/canvas-design/SKILL.md

Quality

Content

48%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 two-phase creative workflow with worked examples and a refinement pass, but is verbose with heavy deliberate repetition and relies on an unbundled ./canvas-fonts reference, weakening token efficiency and actionability.

Suggestions

Collapse the repeated craftsmanship language into a single stated principle and remove the duplicated ESSENTIAL PRINCIPLES restatement to recover token budget.

Either bundle a ./canvas-fonts directory (or a FONTS.md listing recommended fonts) or replace the reference with concrete, self-contained font guidance.

Move the five PHILOSOPHY EXAMPLES into a references/EXAMPLES.md file and signal it one level deep from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose and padded: it instructs craftsmanship to be 'emphasized REPEATEDLY' and restates 'meticulously crafted / painstaking / countless hours / top of their field' across CRITICAL GUIDELINES, ESSENTIAL PRINCIPLES, CANVAS CREATION, and FINAL STEP, with ESSENTIAL PRINCIPLES largely restating earlier points.	2 / 5
Actionability	Provides concrete structure (name the movement 1-2 words, 4-6 paragraphs, worked philosophy examples, output formats) but key guidance is incomplete, e.g. 'Search the ./canvas-fonts directory' and 'Download and use whatever fonts are needed' reference a directory that is not bundled.	3 / 5
Workflow Clarity	A clear two-step sequence (Design Philosophy Creation as .md, then Canvas Creation as .pdf/.png) plus a deducing-the-reference step and a FINAL STEP refinement pass with a self-check ('nothing overlaps, formatting is flawless'); not a 5 because validation is implicit rather than an explicit checkpoint.	4 / 5
Progressive Disclosure	Some structure via section headers, but it is a monolithic ~125-line document with a long inline PHILOSOPHY EXAMPLES block that could live in a separate file, and its only external reference (./canvas-fonts) is not actually bundled, so navigation is not clearly signaled.	3 / 5
	Total	12 / 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-ish what (creating visually-expressed design philosophies as .md/.pdf/.png) but omits any when-to-use trigger guidance, capping completeness. Trigger terms are niche rather than natural user phrasing.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when the user asks for a design philosophy, aesthetic movement, or visually-expressed art concept').

Include synonyms and concrete user phrasings (e.g., 'design manifesto', 'visual art movement', 'poster/cover aesthetic') to improve trigger term coverage.

Tighten the action list to concrete capabilities (e.g., 'write a movement manifesto as .md and render it as a single-page .pdf/.png canvas') for stronger specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ("creating design philosophies - aesthetic movements") and one concrete action ("EXPRESSED VISUALLY" / "Output only .md files, .pdf files, and .png files"), but the actions are minimal and not comprehensive, matching the 3-anchor.	3 / 5
Completeness	Has a clear "what" (creating visually-expressed design philosophies with specific output file types) but no "Use when..." clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant keywords like "design philosophies" and "aesthetic movements" but these are niche artistic terms rather than natural user trigger phrases, and common synonyms/variations are missing; not a 2 because the terms are at least domain-relevant.	3 / 5
Distinctiveness Conflict Risk	The art/design-philosophy niche with fixed output types (.md/.pdf/.png) is mostly distinct with only minor overlap risk against general design skills, fitting just above the 3-anchor.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/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.