CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

29

Quality

22%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-bundle-web-designer/skills/canvas-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

27%Scale 1-3

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

This skill is highly repetitive and verbose, restating the same core ideas (minimal text, visual expression, expert craftsmanship) across nearly every section. While it provides a clear two-step creative workflow with useful philosophy examples, it lacks concrete technical guidance for the actual canvas/PDF/PNG generation and would benefit enormously from deduplication and splitting into referenced sub-files. The skill reads more like an inspirational creative brief than an actionable technical instruction set.

Suggestions

Deduplicate aggressively: the craftsmanship emphasis, minimal-text principle, and visual-expression mandate are each stated 4-6 times. State each once clearly and remove all repetitions to cut the skill by ~40%.

Add concrete technical guidance for canvas creation: specify which tools/libraries to use (e.g., matplotlib, PIL, reportlab), include executable code snippets for PDF/PNG generation, and reference specific font file paths.

Split into multiple files: move philosophy examples to EXAMPLES.md, canvas creation details to CANVAS.md, and multi-page instructions to MULTIPAGE.md, keeping SKILL.md as a concise overview with clear references.

Add a validation checkpoint between philosophy creation and canvas creation (e.g., verify the .md file exists and contains required sections before proceeding to visual output).

DimensionReasoningScore

Conciseness

Extremely verbose and repetitive. The instruction to emphasize craftsmanship is itself repeated at least 5-6 times across different sections. Many paragraphs restate the same ideas (minimal text, visual expression, spatial communication) in slightly different words. The philosophy examples, while useful, are followed by bullet points that repeat the same concepts. The skill explains concepts Claude already understands (what a design philosophy is, what an art movement is) and includes motivational language ('This is true art') that wastes tokens.

1 / 3

Actionability

The skill provides a structured two-step process and gives concrete examples of philosophy names and descriptions, which is helpful. However, it lacks executable code or specific commands for PDF/PNG generation (no library references, no code snippets for canvas creation). The instruction to 'search the ./canvas-fonts directory' is somewhat concrete but the actual visual creation process is described abstractly ('create museum or magazine quality work') rather than with specific tool calls or code patterns.

2 / 3

Workflow Clarity

The two-step workflow (philosophy creation → canvas creation) is clearly sequenced, and there's a refinement pass at the end. However, there are no validation checkpoints between steps, no error recovery guidance, and the 'FINAL STEP' refinement pass lacks concrete criteria for what 'pristine' means or how to verify quality. The 'DEDUCING THE SUBTLE REFERENCE' step is vaguely positioned between the two main steps without clear integration into the workflow.

2 / 3

Progressive Disclosure

The entire skill is a monolithic wall of text with no references to external files despite being quite long. The philosophy examples, canvas creation guidelines, multi-page options, and refinement instructions could all be split into separate referenced documents. The only external reference is './canvas-fonts' directory. The content is poorly organized with redundant sections and no clear navigation structure.

1 / 3

Total

6

/

12

Passed

Description

17%Scale 1-3

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 too vague about what concrete actions the skill performs and completely lacks trigger guidance ('Use when...'). While the domain of 'design philosophies' and 'aesthetic movements' provides some niche identity, the absence of natural user-facing keywords and explicit selection criteria makes it difficult for Claude to reliably choose this skill from a pool of alternatives.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'design philosophy', 'aesthetic style', 'visual movement', 'art direction', 'style exploration'.

Replace vague phrasing like 'expressed visually' with specific actions such as 'generates style guides, mood boards, color palettes, and visual examples of aesthetic movements'.

Include natural keyword variations a user might say, such as 'design style', 'visual aesthetic', 'art style', 'creative direction', or 'design language'.

DimensionReasoningScore

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 specify concrete steps like 'generate mood boards', 'write style guides', or 'render visual examples'.

2 / 3

Completeness

The 'what' is partially addressed but vague, and there is no 'when' clause or explicit trigger guidance at all. The absence of a 'Use when...' clause caps this at 2 per the rubric, and the weak 'what' brings it down 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 unlikely to match common user queries. Missing terms like 'design style', 'visual aesthetic', 'art movement', 'style guide', or 'mood board'.

1 / 3

Distinctiveness Conflict Risk

The combination of 'design philosophies' and 'aesthetic movements' is somewhat distinctive, but the mention of generating .md, .pdf, and .png files is very broad and could overlap with many other creative or design-related skills.

2 / 3

Total

6

/

12

Passed

Validation

90%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
popey/claude-code-skills
Reviewed

Table of Contents

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.