image-enhancer
Improves the quality of images, especially screenshots, by enhancing resolution, sharpness, and clarity. Perfect for preparing images for presentations, documentation, or social media posts.
51
28%
Does it follow best practices?
Impact
88%
1.22xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/image-enhancer/SKILL.mdQuality
Discovery
50%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 communicates the general purpose of the skill (image quality enhancement) and lists some specific attributes it improves, but it lacks an explicit 'Use when...' clause and misses common user trigger terms like 'upscale', 'blurry', or 'low resolution'. It's functional but would benefit from more concrete triggers and clearer selection guidance to stand out among similar image-related skills.
Suggestions
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to upscale, sharpen, or improve a blurry or low-resolution image.'
Include common user-facing terms like 'upscale', 'blurry', 'low quality', 'pixelated', 'enhance photo', and file extensions like '.png', '.jpg' to improve trigger term coverage.
Rewrite 'Perfect for preparing images for presentations...' to use third-person action-oriented language and explicit triggers rather than marketing-style phrasing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (image quality improvement) and some actions (enhancing resolution, sharpness, clarity), but doesn't list multiple concrete distinct actions—it's mostly variations of 'enhance'. It also mentions use cases (presentations, documentation, social media) which adds some specificity. | 2 / 3 |
Completeness | The 'what' is reasonably covered (enhancing image resolution, sharpness, clarity). However, there is no explicit 'Use when...' clause or equivalent trigger guidance—the 'Perfect for...' phrase only implies use cases rather than providing explicit selection triggers. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'screenshots', 'images', 'resolution', 'sharpness', 'presentations', 'documentation', and 'social media posts', but misses common user terms like 'upscale', 'blurry', 'low quality', 'enhance image', 'sharpen', or file format terms like '.png', '.jpg'. | 2 / 3 |
Distinctiveness Conflict Risk | It's somewhat specific to image enhancement/upscaling, but could overlap with general image editing or processing skills. The mention of 'screenshots' adds some distinction, but the description is broad enough to conflict with other image manipulation skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a marketing description rather than actionable technical guidance. It describes what image enhancement looks like conceptually but provides no executable code, no specific tools or libraries (e.g., Pillow, ImageMagick, waifu2x), and no concrete implementation steps. Claude would be left to guess how to actually perform image enhancement.
Suggestions
Add concrete, executable code using a specific library (e.g., Pillow/PIL for sharpening, or ImageMagick commands for upscaling) so Claude knows exactly what tools and methods to use.
Replace the fabricated output example with actual working code that demonstrates the enhancement pipeline end-to-end.
Remove redundant sections ('When to Use', 'Common Use Cases', and 'Tips' overlap significantly) and eliminate explanations of obvious concepts to reduce token waste.
Add validation steps such as checking output image dimensions, verifying file integrity, and comparing before/after quality metrics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose with extensive lists of use cases, tips, and descriptions that add no actionable value. It explains obvious concepts ('takes your images and screenshots and makes them look better') and repeats information across multiple sections (use cases listed twice). Much of this content is padding. | 1 / 3 |
Actionability | There is zero executable code, no specific tools or libraries mentioned, no commands to run, and no concrete implementation guidance. The 'example' is a fabricated output log, not actual code. Claude would have no idea what tool, library, or approach to use to actually enhance an image. | 1 / 3 |
Workflow Clarity | The 'What This Skill Does' section lists abstract steps (analyzes, enhances, improves) without any concrete sequence, commands, validation checkpoints, or error handling. There is no actual workflow—just a description of desired outcomes with no path to achieve them. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with headers, which provides some structure. However, there are no references to external files, no bundle files, and content that could be condensed (like the duplicate use case listings) is left inline. The organization exists but is inefficient. | 2 / 3 |
Total | 5 / 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
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
857fe3a
- 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.