venice-image-edit

Image edits, upscaling, and background removal via the Venice.ai API.

Quality

53%

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/venice-image-edit/SKILL.md

Quality

Content

47%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 a well-organized, concise catalogue stub, but it provides almost no actionable guidance for the skill's actual purpose: no API usage, no code, no concrete install steps, and no validation. Its usefulness as a SKILL.md hinges entirely on an external repository the agent is merely told to open.

Suggestions

Replace the generic "open the upstream URL" instruction with concrete, executable install steps (e.g., an actual git clone or copy command into the skills directory) and a verification step that the skill is discoverable.

Inline a minimal quick-start example for the core task (e.g., a sample Venice.ai image-edit or upscale API call) so the skill is usable without fetching the upstream bundle.

Trim the meta-commentary about the OpenDesign catalogue entry, which does not help the agent execute image edits, and clarify what to do after installation.

Dimension	Reasoning	Score
Conciseness	The body is lean with short, unpadded sections ("What it does", "Source", "How to use") and assumes Claude's competence. Not 5 because the meta-commentary "This catalogue entry advertises the skill in OpenDesign so the agent discovers it during planning" does not help execute the task and could be trimmed.	4 / 5
Actionability	The only concrete instruction is "open https://github.com/veniceai/skills" and "install the upstream bundle" with no commands, code, or paths for actually performing an image edit, upscale, or background removal. This matches "minimal concrete guidance; high-level hints but missing the specific steps" — above 1 only because the upstream URL and invocation-by-name guidance are at least concrete pointers.	2 / 5
Workflow Clarity	A rough sequence exists (inspect upstream README → install bundle into skills directory → invoke by name or trigger), but each step is poorly defined (no clone/copy commands, no verification that the skill installed correctly) and there are no validation checkpoints. Matches the anchor 2 example of a rough sequence with gaps.	2 / 5
Progressive Disclosure	Sections are well organized and the sole reference (the upstream repo URL) is clearly signaled under "Source" with no nested references; no bundle files exist to misplace content. Not 5 because the body is a stub — the actual detailed material lives in an external repo rather than in well-structured one-level-deep local reference files, so there is nothing to navigate locally.	4 / 5
	Total	12 / 20 Passed

Description

58%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 and names three concrete capabilities tied to a specific API, but it omits any "use when" trigger guidance and lacks synonyms/variations of its trigger terms. Adding an explicit use-when clause with natural user phrasings would raise completeness and trigger-term quality.

Suggestions

Append a use-when clause such as "Use when the user wants to edit or upscale an image, or remove/replace an image background, especially with Venice.ai" to fix the missing trigger guidance that caps completeness at 3.

Add natural trigger variations and synonyms ("remove the background", "upscale", "enhance resolution", "transparent background") to broaden keyword coverage.

Mention the concrete deliverable or context (e.g., "for images destined for OpenDesign artifacts") to further sharpen distinctiveness from generic image-editing skills.

Dimension	Reasoning	Score
Specificity	"Image edits, upscaling, and background removal via the Venice.ai API" lists three concrete actions and the specific service, matching the 'several specific actions; minor gaps' anchor. Not 5 because "image edits" is broad and coverage of capabilities (e.g., supported formats, styles) is incomplete.	4 / 5
Completeness	The "what" is clear (edits, upscaling, background removal via Venice.ai) but there is no "Use when..." or equivalent trigger guidance, capping completeness at 3 per the rubric guideline. It is above 2 because the what is specific rather than vague.	3 / 5
Trigger Term Quality	"image edits", "upscaling", and "background removal" are natural phrases users would say, but common variations and synonyms ("remove the background", "upscale an image", "enhance", image extensions) are missing. Fits the 'some relevant keywords but missing common variations' anchor better than 4.	3 / 5
Distinctiveness Conflict Risk	"via the Venice.ai API" establishes a clear niche that distinguishes it from generic image skills; only minor overlap risk with other image-generation/editing skills. Not 5 because "image edits" alone could collide with other image-editing skills if the Venice qualifier is missed.	4 / 5
	Total	14 / 20 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/venice-image-edit/SKILL.md
Commit: 1b47e60

Reviewed: 3 days 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.