pixel-art
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.
64
77%
Does it follow best practices?
Impact
—
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 concrete SVG recipes and a clear pixel grid system that Claude can directly use. Its main weaknesses are moderate verbosity in the recipe sections (hardcoded coordinates that serve more as examples than templates) and a monolithic structure that could benefit from splitting detailed recipes into separate reference files. The workflow section is adequate but could include more explicit validation steps.
Suggestions
Add a validation checkpoint in the workflow, e.g., 'Verify viewBox matches content bounds by checking max x/y of all elements before previewing'
Consider extracting the Chat Bubble Recipe and Arrow Recipe into a separate RECIPES.md reference file to keep the main skill leaner and improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is fairly detailed and mostly earns its place, but some sections like the full chat bubble recipe and arrow recipe are quite verbose with hardcoded pixel coordinates that may not generalize well. The character template and color palette sections are efficient and useful. Some tightening is possible. | 2 / 3 |
Actionability | The skill provides fully executable SVG code snippets — character templates with exact pixel dimensions, complete chat bubble XML, arrow marker definitions, and a concrete grid system. The recipes are copy-paste ready and specific enough to produce working output. | 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 step to verify SVG validity, check for rendering issues programmatically, or validate viewBox bounds before showing to the user. For a creative/visual task this is less critical, but the 'open for preview' step is the only verification. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear headers and logical sections, but it's a monolithic file with no references to external files. The chat bubble recipe, arrow recipe, and character template could be split into separate reference files to keep the main skill leaner. For a skill of this length (~120 lines of substantive content), some splitting would improve navigability. | 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 | |
- Commit
a425a71
- 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.