venice-image-generate

Image generation endpoints and available styles via the Venice.ai API.

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

Quality

Content

40%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 lean, organized catalogue stub, but it delivers no executable guidance: the sole command is non-portable, the install step is unspecified, and all substantive content is deferred to an external URL. Sections duplicating frontmatter add tokens without value.

Suggestions

Replace the 'open <url>' snippet with a concrete, executable install step (e.g. a git clone or copy command with the real target path in the agent's skills directory).

Include at least one minimal executable example of the skill's actual purpose (e.g. a sample Venice.ai image-generation API call or the invocation syntax) so the entry is actionable without leaving the environment.

Remove the 'What it does' and 'Source' sections that duplicate the description and frontmatter verbatim, tightening the entry to the essential usage instructions.

Dimension	Reasoning	Score
Conciseness	The body is short and free of concept explanations Claude already knows, but it is redundant: 'What it does' repeats the description verbatim and the 'Source' section duplicates the frontmatter upstream/category fields. It is not a 4 because those duplicative sections could simply be cut.	3 / 5
Actionability	The only command is 'open https://github.com/veniceai/skills', which is not executable on most Linux shells and performs no installation, and the instruction to 'install the upstream bundle' gives no actual command, path, or mechanism. It is not a 3 because there is no partially-executable concrete step — no real code, command, or API example at all.	2 / 5
Workflow Clarity	A rough sequence exists (inspect upstream README, install the bundle, invoke by name or trigger), but the critical install step is undefined and there are no checkpoints or verification of success. It is not a 3 because the middle step — the actual task — is a gap rather than merely an implicit checkpoint.	2 / 5
Progressive Disclosure	No bundle files exist (no references/, scripts/, or assets/), and the under-50-line body is organized into clear sections with a single one-level pointer to the upstream repo. It is not a 5 because the pointer goes to an external URL with no local reference structure, and the overview itself carries almost no content.	4 / 5
	Total	11 / 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.

A terse, reasonably specific description that clearly states what the skill covers, but it lacks any 'when to use' trigger guidance within the description field itself and misses common natural-language variations of the core terms.

Suggestions

Add an explicit trigger clause to the description, e.g. 'Use when the user asks to generate or stylize images with Venice.ai or mentions Venice image generation.'

Include concrete actions and natural variations in the description text: 'Generate images, apply styles, and list available styles via the Venice.ai API (text-to-image, AI image creation).'

Fold the frontmatter trigger phrases ('venice image', 'venice generate') or their natural-language equivalents into the description so discovery does not depend on a separate field.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Venice.ai API') and 1-2 concrete capabilities ('Image generation endpoints', 'available styles'), but as noun phrases with no explicit actions. It is not a 4 because it does not list several specific actions, and not a 2 because it goes beyond a bare domain label.	3 / 5
Completeness	It has a clear 'what' (image generation endpoints and styles via the Venice.ai API) but no 'Use when...' clause or equivalent explicit trigger guidance inside the description, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'Image generation', 'Venice.ai', and 'styles' are natural terms a user might say, but the description itself omits common variations and synonyms ('create image', 'text-to-image', 'AI image'). The fuller trigger phrases exist only in the separate frontmatter triggers field, not in the description text.	3 / 5
Distinctiveness Conflict Risk	'Venice.ai' branding carves a clear niche with minimal conflict risk. It is not a 5 because it could still overlap with other generic image-generation skills when the provider is unstated.	4 / 5
	Total	13 / 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-generate/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.