Generate pixel art SVG illustrations for READMEs, docs, or slides. Use when user says "画像素图", "pixel art", "make an SVG illustration", "README hero image", or wants a cute visual.
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/pixel-art/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger terms spanning multiple languages and natural phrasings, a clear 'Use when' clause, and a distinctive niche. The main weakness is that the 'what' portion could be more specific about the range of concrete actions beyond just 'generate'.
Suggestions
Expand the capability list with more specific actions, e.g., 'Generate pixel art SVG illustrations including characters, icons, banners, and scene art for READMEs, docs, or slides.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (pixel art SVG illustrations) and the output contexts (READMEs, docs, slides), but doesn't list multiple concrete actions beyond 'generate'. It could specify more actions like 'design characters', 'create icons', 'animate sprites', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (generate pixel art SVG illustrations for READMEs, docs, or slides) and 'when' (explicit 'Use when' clause with specific trigger phrases). Both components are well-defined. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: '画像素图', 'pixel art', 'make an SVG illustration', 'README hero image', and 'cute visual'. These cover multiple languages and natural phrasings a user would actually say. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'pixel art' + 'SVG' + specific use cases like 'README hero image' creates a clear niche that is unlikely to conflict with general illustration, SVG manipulation, or documentation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, highly actionable skill with excellent concrete examples including exact pixel dimensions, color codes, and copy-paste SVG snippets. Its main weaknesses are that it's somewhat long for a single SKILL.md file — the detailed recipes could be split into referenced files — and the workflow section lacks explicit validation checkpoints before presenting output to the user. The common pitfalls section is a strong addition that adds practical value.
Suggestions
Add an explicit validation checkpoint in the workflow, e.g., 'Verify: check that viewBox matches content bounds, no overlapping elements, all text fits within bubbles' before showing to user.
Consider moving the detailed Chat Bubble Recipe, Arrow Recipe, and Character Template sections into a referenced file (e.g., RECIPES.md) to keep SKILL.md as a concise overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is fairly efficient and avoids explaining basic SVG concepts, but some sections like the character template and multiple recipe blocks are quite lengthy. The color palette section lists many options that could be trimmed. Overall mostly efficient but could be tightened. | 2 / 3 |
Actionability | Highly actionable with concrete, copy-paste-ready SVG code snippets for chat bubbles, arrows, character templates with exact pixel dimensions, and specific color hex codes. The character template gives exact row-by-row pixel placement instructions. | 3 / 3 |
Workflow Clarity | The 4-step workflow is clearly sequenced and includes an iteration loop with the user, but lacks explicit validation checkpoints. There's no verification step to check SVG validity or rendering correctness before showing to the user — just 'open with open <file.svg>' without checking for common errors first. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, but it's a monolithic file with ~120 lines of detailed recipes and templates that could be split into referenced files (e.g., CHARACTER_TEMPLATES.md, BUBBLE_RECIPES.md). For a skill of this complexity, some content should be externalized. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
700fbe2
Table of Contents
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.