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 well-structured but essentially pointer-style catalogue entry that advertises an upstream skill rather than containing the workflow itself, so it is lean and navigable but lacks concrete install/action steps.

Suggestions

Replace the vague 'install the upstream bundle' with concrete, copy-paste-ready commands (e.g., a git clone into the skills directory with the exact target path).

Spell out the invocation workflow as numbered steps with a verification checkpoint confirming the skill is discoverable after install.

Inline at least a minimal example of calling the Venice.ai video/transcription endpoint so the skill is actionable without leaving for the upstream repo.

Dimension	Reasoning	Score
Conciseness	The body is short, lean, and avoids explaining concepts Claude already knows; the only minor trim is the description line repeated under 'What it does', so it sits just below the fully lean anchor at 5.	4 / 5
Actionability	Concrete guidance is minimal: the only executable line is `open https://github.com/veniceai/skills`, while the actual instruction ('install the upstream bundle into your active agent's skills directory') is a high-level hint with no specific install command, matching the 'minimal concrete guidance; missing specific steps' anchor.	2 / 5
Workflow Clarity	A rough sequence is implied (inspect README -> install bundle -> invoke by name/trigger) but the install step is undefined and there are no checkpoints; this fits the 'rough sequence present but many gaps; steps poorly defined' anchor better than the more concrete anchor at 3.	2 / 5
Progressive Disclosure	Well-organized sections (What it does, Source, How to use) with a single, clearly signaled one-level-deep external reference (the upstream repo); not a 5 because all substantive content lives externally rather than in well-split local files.	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 clear and specific to a named API but reads as a terse capability statement rather than a trigger-optimized skill description, omitting any 'Use when...' guidance that would help with discovery.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when generating video from prompts or transcribing audio via Venice.ai').

Replace the generic word 'workflows' with specific actions such as 'generate video from text/image prompts' and 'transcribe audio files'.

Include natural synonyms and file extensions users might say (e.g., 'text-to-video', 'speech-to-text', .mp4, .wav) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete capability types ("Video generation" and "transcription") tied to a named API, but the generic word "workflows" leaves the specific actions under-described, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Provides a clear 'what' (video generation and transcription workflows via the Venice.ai API) but no 'Use when...' clause or equivalent trigger guidance; per the rubric guideline a missing 'when' caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant natural terms ("video generation", "transcription", "Venice.ai") but misses common variations and synonyms such as "create video", "text-to-video", or "speech to text", fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific vendor API ("Venice.ai") and two clearly scoped domains, making it mostly distinct with only minor overlap risk against generic video or transcription skills; not a 5 because the two broad domains still leave some overlap with related skills.	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: 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.