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

37%

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

The body is token-efficient and neatly sectioned, but it functions as a stub that points to an external repository rather than providing executable install steps, a concrete workflow, or any inline usage example.

Suggestions

Replace the `open https://github.com/...` URL-open with a concrete, executable install command (e.g., a git clone / copy step into the agent's skills directory) so the body instructs rather than points.

Lay out an explicit sequenced workflow (install upstream bundle → load into skills dir → invoke by name or trigger) with concrete commands instead of vague prose.

Inline at least a minimal usage example (e.g., a sample Venice.ai API call or a worked trigger invocation) so the body has standalone value without requiring the external README.

Dimension	Reasoning	Score
Conciseness	The body is short and lean, does not explain concepts Claude already knows, and avoids padding, matching the 'lean and efficient; every token earns its place' anchor rather than the tighter-could-be anchor at 2.	3 / 3
Actionability	The only command is `open https://github.com/veniceai/skills`, which opens a URL rather than executing the workflow, and the install instructions are vague prose — matching the 'describes rather than instructs; no concrete code/commands' anchor at 1.	1 / 3
Workflow Clarity	The 'How to use' section offers loose prose ('install the upstream bundle into your active agent's skills directory') with no concrete sequenced steps or validation, fitting the 'steps unclear or missing' anchor at 1 rather than the listed-but-gappy anchor at 2.	1 / 3
Progressive Disclosure	Sections are well organized for a short entry, but all real content lives off-repo behind a single external GitHub pointer with no local bundle files, fitting the 'could be better organized; references present but not richly signaled' anchor at 2 rather than the clean one-level-deep local-reference structure at 3.	2 / 3
	Total	7 / 12 Passed

Description

75%

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 concrete, natural-sounding capabilities, but it omits an explicit 'when to use' clause and does not establish fully distinct triggers within the description text.

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 satisfy the 'when' half of completeness.

Sharpen 'image edits' into concrete operations (e.g., 'style transfers, inpainting, variations') to reduce overlap with generic image skills and raise distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names multiple concrete actions — "Image edits, upscaling, and background removal" — and ties them to the Venice.ai API, matching the 'lists multiple specific concrete actions' anchor rather than the vague single-domain anchor at 2.	3 / 3
Completeness	It clearly answers 'what' (edits/upscaling/background removal via the API) but provides no 'Use when...' clause or explicit trigger guidance, so per the rubric guideline completeness is capped at 2 rather than reaching 3.	2 / 3
Trigger Term Quality	Terms like "image edits", "upscaling", and "background removal" are natural phrases a user would say when requesting this skill, giving good coverage rather than the partial keyword set at 2.	3 / 3
Distinctiveness Conflict Risk	The Venice.ai API scoping is somewhat specific, but the image-editing domain broadly overlaps other image skills and no distinct triggers are stated in the description itself, fitting the 'could still overlap' anchor at 2 rather than a clear niche at 3.	2 / 3
	Total	10 / 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/venice-image-edit/SKILL.md
Commit: a2ba3ee

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