venice-image-generate

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

Quality

48%

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

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 tidy, well-sectioned pointer to an upstream bundle rather than a self-contained skill: it is concise and easy to navigate but offers almost no executable guidance or concrete workflow. Its value depends entirely on the user fetching the external upstream repository.

Suggestions

Provide a concrete install command or step for placing the upstream bundle into the agent's skills directory instead of just 'install the upstream bundle'.

Add at least one executable example of invoking the Venice.ai image-generation endpoint so the skill is usable without fetching upstream.

Include a verification step (e.g. how to confirm the skill is registered and the trigger phrases resolve) so the rough install-invoke workflow has a checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is lean and uses clear sections without explaining concepts Claude already knows; the one mild instance of padding ('This catalogue entry advertises the skill in OpenDesign so the agent discovers it during planning') keeps it just below the fully-trimmed 5.	4 / 5
Actionability	Beyond the trivial `open https://github.com/veniceai/skills` command, guidance is high-level ('install the upstream bundle', 'ask the agent to invoke this skill by name') with no specific executable steps, matching 'Minimal concrete guidance; high-level hints but missing the specific steps to execute'.	2 / 5
Workflow Clarity	A rough sequence is present in prose (advertise in OpenDesign, install the upstream bundle, invoke by name) but the install step is undefined and there are no checkpoints or validation, fitting 'Rough sequence present but many gaps; steps poorly defined; validation absent'.	2 / 5
Progressive Disclosure	Content is organized into well-labeled sections (What it does, Source, How to use) with a single one-level-deep external reference (the upstream URL) and no nested references; it falls just short of a 5 because the upstream-pointer structure leaves the real detail external rather than clearly split local files.	4 / 5
	Total	12 / 20 Passed

Description

48%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 a concise, distinct noun phrase that clearly scopes the skill to Venice.ai image generation, but it is purely descriptive and omits both concrete actions and an explicit 'Use when' trigger clause. It reads more like a catalogue label than a self-contained trigger description.

Suggestions

Add an explicit trigger clause, e.g. 'Use when generating images via the Venice.ai API or when the user asks for Venice image generation styles.'

Replace the static noun phrase with concrete actions the skill performs, e.g. 'Generates images and lists available styles via the Venice.ai API.'

Include natural synonym variations such as 'text-to-image' or 'generate images' to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Image generation endpoints and available styles via the Venice.ai API' names the domain and surfaces objects (endpoints, styles) but lists no concrete actions the skill performs, matching 'Names the domain but actions are minimal or generic'; it does not reach the 1-2 concrete actions needed for a 3.	2 / 5
Completeness	The description gives a clear 'what' but no 'Use when...' trigger guidance; per the guideline, a missing explicit trigger clause caps completeness at 3, so it does not reach 4 which requires both what and when.	3 / 5
Trigger Term Quality	'Image generation', 'styles', and 'Venice.ai API' are relevant natural keywords a user might say, but common variations and synonyms (e.g. 'generate images', 'text-to-image', file extensions) are missing, fitting 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	Tying the entry to the Venice.ai API and image generation gives it a clear niche with minimal conflict risk, but it could still overlap with other Venice.ai skills, fitting 'Mostly distinct; minor overlap risk with closely related skills' rather than the fully-distinct 5.	4 / 5
	Total	12 / 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: 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.