image-enhancer

Improve image and screenshot quality by enhancing resolution, sharpness, and clarity for professional presentations and documentation.

Quality

46%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/image-enhancer/SKILL.md

Quality

Content

57%

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

The body is concise and well-organized but functions only as a pointer to an external upstream bundle, offering no executable guidance or real workflow. It scores well on token efficiency and structure but fails on actionability.

Suggestions

Provide at least one concrete, executable step (e.g. a git clone or install command with the actual upstream path) instead of just opening a URL in a browser.

Add a brief inline workflow for the common case (install bundle, then invoke by name or trigger) with a verification checkpoint that the skill is available.

If the real instructions live only upstream, inline the minimal first-run commands so the skill is usable without leaving the SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows; every section (What it does, Source, How to use) earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	It offers no executable code or concrete commands — only 'open https://...' and 'ask the agent to invoke this skill', which describes rather than instructs, matching the 'vague or abstract; no concrete code' anchor.	1 / 3
Workflow Clarity	The body has no multi-step sequence; the install instruction is a single abstract action with no validation checkpoints, sitting at the 'steps present but checkpoints missing/implicit' level at best.	2 / 3
Progressive Disclosure	Under 50 lines with well-organized sections and no nested references, so per the simple-skills scoring note progressive disclosure can score 3 on organization alone.	3 / 3
	Total	9 / 12 Passed

Description

35%

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 clearly states the skill's purpose in third person with concrete capability language, but lacks any explicit when-to-use clause and omits natural trigger keywords within the description text. It is reasonably distinguishable but somewhat broad.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when the user asks to upscale, sharpen, denoise, or otherwise improve an image or screenshot.'

Weave natural trigger terms (upscale, sharpen, denoise, improve image quality) into the description text rather than relying solely on the separate triggers list.

Tighten distinctiveness by pairing the capability with the specific output context (e.g. 'for professional presentations and documentation') more clearly as a trigger signal.

Dimension	Reasoning	Score
Specificity	Names the image domain and concrete actions ('enhancing resolution, sharpness, and clarity'), but these are variations of a single capability rather than multiple distinct actions, matching the 'domain and some actions' anchor.	2 / 3
Completeness	It states what the skill does but includes no 'Use when...' or equivalent explicit when-to-use clause, so completeness is capped at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	The description itself contains no natural trigger keywords a user would say (terms like 'enhance image', 'upscale', 'denoise' appear only in the frontmatter triggers list, not in the description), leaving it with no in-description natural keywords.	1 / 3
Distinctiveness Conflict Risk	'Improve image and screenshot quality' is somewhat specific to image enhancement but could still overlap with general image-generation or image-editing skills, matching the 'somewhat specific but could overlap' anchor.	2 / 3
	Total	7 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/image-enhancer/SKILL.md
Commit: f2760fd

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

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.