canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

Quality

55%

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

The canonical home for this skill is openakita/skills@canvas-design in openakita/openakita

Quality

Content

35%

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

The skill is well-structured as a two-phase creative workflow but suffers from heavy verbosity, repeated motivational padding, and an absence of concrete rendering guidance or validation steps. It also points at a non-existent ./canvas-fonts directory.

Suggestions

Remove the repeated craftsmanship emphasis—state the 'expert, labored-over' quality once and trust it; cut poetic filler like 'treat the abstract philosophical design as if it were a scientific bible' to earn back token budget.

Add a concrete, named rendering path: specify the tool/library or approach for generating the .pdf/.png (e.g., a script in ./scripts/ or a documented library), and include at least one executable example or command.

Add a verification checkpoint before output—e.g., confirm nothing overlaps, elements sit within margins, and text/fonts are loaded—so the workflow has a validate-then-fix loop, and either create the referenced ./canvas-fonts directory or remove the dangling reference.

Dimension	Reasoning	Score
Conciseness	The body is padded with repeated craftsmanship exhortations ('meticulously crafted', 'countless hours', 'top of their field' appear multiple times) and poetic filler such as 'treat the abstract philosophical design as if it were a scientific bible', restating ideas Claude already grasps and re-emphasizing points with 'CRITICAL'/'IMPORTANT'/'VERY IMPORTANT' labels.	1 / 3
Actionability	Some concrete guidance is present (output only .md/.pdf/.png, name the movement in 1-2 words, 4-6 paragraph philosophy, search ./canvas-fonts), but the core production mechanism—how to actually render a .pdf or .png—is never specified; no tool, library, or executable code is named.	2 / 3
Workflow Clarity	The two-step sequence (1. design philosophy .md, 2. canvas .pdf/.png) plus a refinement pass is laid out, but there are no validation or verification checkpoints; the 'final step' refinement is editorial polish rather than a validate-fix-retry loop.	2 / 3
Progressive Disclosure	The single SKILL.md is organized into clear sections, but it references a './canvas-fonts' directory that does not exist in the bundle, and no references/, scripts/, or assets/ structure is present to split the lengthy inline examples and philosophy guidance.	2 / 3
	Total	7 / 12 Passed

Description

75%

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 clearly communicates both its purpose and explicit use-conditions with a distinct, low-conflict niche. Its main weaknesses are the second-person voice (which costs a specificity point) and somewhat limited trigger-term variation.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('create a poster, piece of art, design, or other static piece') and names the .png/.pdf medium, which would rate 3, but the second-person phrasing 'You should use this skill' triggers the one-point specificity reduction per the judging guidelines, bringing it to 2.	2 / 3
Completeness	Explicitly states what it does ('Create beautiful visual art in .png and .pdf documents using design philosophy') and when to use it ('You should use this skill when the user asks to create a poster...'), answering both what and when with an explicit trigger.	3 / 3
Trigger Term Quality	Includes natural terms a user might say ('poster', 'piece of art', 'design', 'static piece') but misses common variations such as 'artwork', 'illustration', 'graphic', or 'flyer', so coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	The niche is clear—static visual art via a design philosophy in .png/.pdf—with triggers (poster, art, design, static piece) that are unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: JetBrains/skills
Path: canvas-design/SKILL.md
Commit: e0f258b

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.