venice-image-edit

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

Quality

56%

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 content is a clean, well-structured catalogue pointer that stays lean, but it provides almost no executable guidance — it delegates the actual image-editing workflow to an upstream README rather than giving concrete API calls or commands.

Suggestions

Add a concrete, copy-paste-ready example of invoking the Venice.ai API for at least one operation (e.g. an upscaling request with endpoint, parameters, and expected response) instead of only linking the upstream repo.

Replace the vague "install the upstream bundle into your active agent's skills directory" with the specific install command(s) and exact target path.

Include a brief validation step (e.g. how to confirm the edit succeeded or inspect the output) to give the rough invoke workflow a checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is short and does not explain concepts Claude already knows, though the "How to use" prose ("This catalogue entry advertises the skill in OpenDesign so the agent discovers it during planning...") and the verbatim repeat of the description under "What it does" are minor over-explanation that could be trimmed.	4 / 5
Actionability	The only concrete command is `open https://github.com/veniceai/skills` (which merely opens a browser), and the rest is high-level hints ("install the upstream bundle", "Inspect the upstream README"); the specific steps to actually perform an image edit, upscale, or background removal are entirely absent.	2 / 5
Workflow Clarity	A rough sequence exists (inspect upstream README → install bundle → invoke by name/trigger), but the steps are poorly defined with many gaps and no validation checkpoints; the real workflow is delegated to the upstream repo.	2 / 5
Progressive Disclosure	The body is a lean, well-organized overview with clear sections (What it does / Source / How to use) and a clearly signaled one-level external reference (the upstream repo URL), with no local bundle files present to misreference; the only gap is that all detail lives in an external URL rather than local reference files.	4 / 5
	Total	12 / 20 Passed

Description

66%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 anchored to a specific API, giving it decent specificity and distinctiveness. Its main weakness is the missing "Use when..." trigger guidance, which caps completeness at 3.

Suggestions

Add an explicit "Use when..." clause (e.g. "Use when the user wants to edit, upscale, or remove backgrounds from images via Venice.ai") to lift completeness beyond 3.

Include natural synonyms and variations ("remove background", "upscale image", "enhance image") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists three named operations — "Image edits, upscaling, and background removal" — which qualifies as several specific actions, though "image edits" remains somewhat broad, leaving minor coverage gaps.	4 / 5
Completeness	The "what" is clear (the three operations via the Venice.ai API), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	"image edits", "upscaling", and "background removal" are natural phrases a user would say, but synonyms (e.g. "remove background", "upscale image", "enhance") and file extensions are absent.	4 / 5
Distinctiveness Conflict Risk	The "via the Venice.ai API" qualifier and the three specific operations give it a clear niche, though broad "image edits" could still overlap with other image skills.	4 / 5
	Total	15 / 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: d4138ea

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.