tessl i github:ComposioHQ/awesome-claude-skills --skill image-enhancerImproves the quality of images, especially screenshots, by enhancing resolution, sharpness, and clarity. Perfect for preparing images for presentations, documentation, or social media posts.
Activation
50%The description provides a reasonable overview of the skill's purpose with some concrete capabilities (resolution, sharpness, clarity enhancement) and use cases. However, it lacks an explicit 'Use when...' clause, misses common trigger terms users would naturally say, and could be more distinctive to avoid conflicts with other image-related skills.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'enhance image', 'improve quality', 'blurry screenshot', 'upscale', 'sharpen photo'
Include file format triggers users might mention: '.png', '.jpg', 'screenshot', 'low-res image'
Make the scope more distinctive by specifying what this skill does NOT do (e.g., not for image generation or artistic editing) to reduce conflict risk with other image skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (image quality improvement) and some actions (enhancing resolution, sharpness, clarity), but lacks comprehensive specific actions like upscaling, denoising, or artifact removal. | 2 / 3 |
Completeness | Describes what it does (improves image quality) and mentions use cases ('Perfect for...'), but lacks an explicit 'Use when...' clause with trigger guidance. The when is implied through examples rather than explicitly stated. | 2 / 3 |
Trigger Term Quality | Includes some relevant terms like 'screenshots', 'images', 'presentations', 'documentation', but misses common variations users might say like 'upscale', 'sharpen', 'blurry', 'low resolution', 'enhance photo', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | Focuses on image enhancement which is somewhat specific, but 'images' is broad and could overlap with other image-related skills (editing, generation, conversion). The screenshot focus helps but isn't strongly distinctive. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
22%This skill describes what image enhancement should accomplish but fails to provide any actual implementation guidance. It reads more like a feature description or marketing copy than an actionable skill. Claude would have no idea what tools, libraries, or commands to use to actually enhance images.
Suggestions
Add concrete executable code using a specific image processing library (e.g., PIL/Pillow, ImageMagick commands, or a specific upscaling tool like Real-ESRGAN)
Replace the conceptual 'What This Skill Does' section with actual implementation steps showing specific commands or code for each enhancement type
Include validation steps to verify image quality before/after enhancement and handle common errors (file not found, unsupported format, insufficient memory for large images)
Remove the 'When to Use This Skill' and 'Common Use Cases' sections - these are obvious and waste tokens
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'When to Use This Skill' with obvious use cases Claude would infer, and 'What This Skill Does' which describes rather than instructs. The tips and common use cases sections add bulk without actionable value. | 2 / 3 |
Actionability | The skill provides no executable code, no specific tools or libraries, and no actual implementation. It only shows example prompts and mock output - Claude wouldn't know HOW to actually enhance images (what tool to use, what commands to run, what parameters to set). | 1 / 3 |
Workflow Clarity | The 'What This Skill Does' section lists conceptual steps but provides no actual workflow for execution. There are no validation checkpoints, no error handling, and no concrete sequence of operations Claude could follow to enhance an image. | 1 / 3 |
Progressive Disclosure | The content is reasonably organized with clear sections, but it's somewhat monolithic with content that could be trimmed. No external references are needed for this scope, but the structure mixes conceptual descriptions with usage examples without clear hierarchy. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
81%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
Reviewed
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.