venice-video

Video generation and transcription workflows via the Venice.ai API.

Quality

50%

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-video/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.

This is a lean, well-organized catalogue stub, but it contains no executable guidance: the actual workflow, assets, scripts, and references all live in an external GitHub repo, and the body gives neither the install steps nor any verification. It reads as an advertisement rather than an actionable skill.

Suggestions

Replace the `open <url>` snippet with the concrete commands needed to fetch and install the bundle (e.g., git clone with the actual repo path, and the target skills-directory path to copy into).

Add an explicit sequence for the How-to-use workflow: install step, verification step (confirm the skill appears/is invocable), then invocation example, so a rough order with checkpoints exists.

Include at least one example invocation (a sample user request plus the expected trigger/skill name) so the 'ask the agent to invoke this skill' guidance is concrete.

Dimension	Reasoning	Score
Conciseness	The body is short (~30 lines) with no padding or explanations of concepts Claude already knows; the only trimmable parts are the 'What it does' section restating the frontmatter description verbatim and the 'Curated from the Venice.ai team' line, so it sits just below the lean-every-token-earns-its-place anchor.	4 / 5
Actionability	The core instruction 'install the upstream bundle into your active agent's skills directory' is a high-level hint with no clone/copy command, path, or install steps, and the only code block (`open https://github.com/veniceai/skills`) merely opens a browser rather than performing the needed action, matching 'minimal concrete guidance; high-level hints but missing the specific steps to execute'.	2 / 5
Workflow Clarity	A rough sequence exists (inspect upstream -> install bundle -> invoke by name or trigger), but 'install the upstream bundle' is undefined, no concrete install steps are given, and there is no verification that the skill was installed or works, matching 'rough sequence present but many gaps; validation absent'.	2 / 5
Progressive Disclosure	Sections (What it does / Source / How to use) are clear and well-organized, no bundle files exist to reference, and the pointer to the upstream repo is well signaled in a dedicated Source section — but the entire substantive content lives behind an external URL rather than appropriately split material, leaving minor organization gaps.	4 / 5
	Total	12 / 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.

The description is concise, in third person, and names a specific vendor API, giving it reasonable distinctiveness. However, it omits any 'when to use' guidance and only gestures at two operations without concrete actions or trigger variations, leaving it at a middling level.

Suggestions

Append an explicit when-clause, e.g., 'Use when the user asks to generate or transcribe video via Venice.ai, or mentions Venice video, venice transcribe, or text-to-video.'

Spell out the concrete capabilities (e.g., 'Generate video from text or image prompts, retrieve video status and results, and transcribe audio/video to text') instead of the generic 'workflows'.

Add natural trigger synonyms users would say — 'make a video', 'text-to-video', 'video from an image', 'captions/transcribe audio' — to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Video generation and transcription workflows via the Venice.ai API' names the domain and two operations (video generation, transcription), but names them as noun phrases with no further concrete actions, matching 'names domain and 1-2 concrete actions, but not comprehensive' rather than score 4's 'several specific actions'.	3 / 5
Completeness	There is a clear 'what' (video generation and transcription via the Venice.ai API) but the description itself has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; the frontmatter triggers field is separate from the description text.	3 / 5
Trigger Term Quality	The description contains the relevant keywords 'Video generation', 'transcription', and 'Venice.ai API', which users would plausibly say, but offers no common variations or synonyms (e.g., 'make a video', 'text-to-video', 'audio-to-text', 'captions'), matching 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific vendor 'Venice.ai API' carves out a mostly distinct niche with only minor overlap risk against generic video-generation or transcription skills; it falls short of anchor 5 because the description lacks distinct trigger phrases and 'video generation'/'transcription' alone are generic capabilities.	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-video/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.