image-editing

Edit an image from the active iPolloWork Image Studio selection or mask without overwriting the source image.

Quality

63%

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 ./.agents/skills/image-editing/SKILL.md

Quality

Content

72%Weight 40%Scale 1-5

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

The body is exceptionally concise and well-structured for a simple instruction-only skill, with a clear sequenced workflow. Its main weakness is missing operational specifics (how to save/return the new image) and absent explicit validation of the source-preservation outcome.

Suggestions

Add the concrete mechanism for saving and returning the edit, e.g. the workspace path format or the save API/command to call in step 4-5.

Insert an explicit validation checkpoint, e.g. "Verify the source image is unchanged and only the masked region was altered before returning the path."

Clarify how to infer the requested target from mask + prompt (step 3) with a brief concrete cue so the ask-for-clarification trigger is unambiguous.

Dimension	Reasoning	Score
Conciseness	Six lean lines with no concept over-explanation; every directive earns its place and Claude's competence is assumed, matching the "lean and efficient; every token earns its place" anchor; not 4 because there are no instances of over-explanation to trim.	5 / 5
Actionability	Gives concrete behavioral directives (change only the requested region, save as a new workspace image, return the path) but omits the operational mechanics for an instruction-only skill (how to save a new workspace image, what path/format to return), fitting the "some concrete guidance but incomplete" anchor; not 4 because key execution details are missing.	3 / 5
Workflow Clarity	A clear five-step sequence exists with one implicit checkpoint (ask for a clearer selection), but there is no explicit validation/verification step for a source-preserving edit operation, so the destructive-adjacent cap holds at 3; not 4 because validation checkpoints are missing rather than minor.	3 / 5
Progressive Disclosure	Under 50 lines with no need for external references and a well-organized heading-plus-numbered-list structure, qualifying for the simple-skill exception at 5; no bundle files exist to require deeper referencing.	5 / 5
	Total	16 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 is concise, third-person, and names a specific product niche with a clear preserve-source constraint, but it omits an explicit "Use when..." trigger clause, which caps completeness. Trigger-term coverage is reasonable but narrow.

Suggestions

Add an explicit trigger clause, e.g. "Use when an image is open in Image Studio and the user asks to edit, retouch, or modify part of it via a selection or mask."

Broaden trigger terms with natural synonyms and extensions (e.g., "retouch", "inpaint", "mask", ".png/.jpg") so users' phrasings match.

List one or two more concrete actions (e.g., "retouch a region", "fill or extend a masked area") to raise specificity beyond a single action.

Dimension	Reasoning	Score
Specificity	Names the image-editing domain and one concrete action ("Edit an image from the active ... selection or mask") plus a preserve-source constraint, but does not enumerate multiple distinct actions, matching the 1-2 concrete actions anchor; not 2 because it is more specific than "Processes PDF files" and not 4 because it lacks several listed actions.	3 / 5
Completeness	Has a clear "what" (edit an image from selection/mask without overwriting source) but no explicit "Use when..." trigger clause, so per the missing-trigger cap it stays at 3; not 4 because the "when" is only weakly implied rather than explicit.	3 / 5
Trigger Term Quality	Includes some natural terms a user would say ("Edit an image", "selection", "mask") but misses common variations, synonyms, and file extensions, fitting the "some relevant keywords but missing common variations" anchor; not 4 because keyword coverage is narrow rather than good.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific product context (iPolloWork Image Studio active selection/mask) with a distinct preserve-source framing, making it mostly distinct with only minor overlap risk against other image skills; not 5 because image editing is a broad domain where closely related skills could still overlap.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Devin-AXIS/iPolloWork
Path: .agents/skills/image-editing/SKILL.md
Commit: dada31d

Reviewed: 13 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.