venice-audio-music

Music generation queueing, retrieval, and completion endpoints via Venice.ai. Suited for jingles, background loops, and prototype scoring.

Quality

58%

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-audio-music/SKILL.md

Quality

Content

51%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 content is a concise, well-structured catalogue/pointer entry but offers little actionable guidance — the install and run steps are undefined and punt to an external README. Progressive disclosure is strong thanks to clean organization and a single upstream pointer.

Suggestions

Replace the URL-opening command with concrete executable install steps (e.g., git clone, copy path, or a real command) so the 'How to use' section is copy-paste ready.

Remove the verbatim duplication of the frontmatter description in the 'What it does' section, or make that section add new information.

Define the invoke workflow explicitly (step list with the exact skill name and a sample trigger phrase) to close the workflow-clarity gaps.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, but the 'What it does' section duplicates the frontmatter description verbatim — a minor redundancy that keeps it at 'efficient; minor instances that could be trimmed' rather than the fully lean 5.	4 / 5
Actionability	Guidance is mostly high-level ('install the upstream bundle into your active agent's skills directory') with only a URL-opening command and an explicit punt ('Inspect the upstream README for exact paths'), missing the specific executable steps to install or run, fitting 'minimal concrete guidance; missing the specific steps'.	2 / 5
Workflow Clarity	A rough sequence exists (inspect README, install bundle, invoke by name) but steps are poorly defined with no concrete install commands or checkpoints, matching 'rough sequence present but many gaps'; it does not reach 3 because the install step is undefined rather than merely unvalidated.	2 / 5
Progressive Disclosure	Under 50 lines with no external bundle files needed; it is cleanly sectioned (What it does, Source, How to use) and points one level out to the upstream repo, meeting the simple-skill exception for a well-organized overview.	5 / 5
	Total	13 / 20 Passed

Description

66%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 specific and domain-clear with good trigger coverage, but lacks an explicit 'Use when...' usage clause, capping completeness at 3. The generic 'score' trigger is the main distinctiveness risk.

Suggestions

Add an explicit 'Use when...' clause to the description (e.g., 'Use when the user needs to generate music, jingles, or background loops via Venice.ai') to lift completeness above 3.

Replace or qualify the generic 'score' trigger to reduce conflict risk with unrelated scoring/grading skills.

Consider adding a synonym or file-extension-style term (e.g., 'music generation', 'audio track') to round out trigger coverage toward 5.

Dimension	Reasoning	Score
Specificity	Names the music-generation domain and several concrete actions ('queueing, retrieval, and completion endpoints') with minor coverage gaps, matching the 'lists several specific actions' anchor rather than the comprehensive 5.	4 / 5
Completeness	It clearly states what the skill does but only weakly implies when to use it ('Suited for jingles, background loops, and prototype scoring') with no explicit 'Use when...' clause, which the guidelines cap at 3.	3 / 5
Trigger Term Quality	The triggers field includes natural terms ('music gen', 'jingle', 'background loop') giving good coverage, though 'score' is generic and 'venice music' is product-specific, so it does not reach comprehensive synonym/extension coverage at 5.	4 / 5
Distinctiveness Conflict Risk	The Venice.ai-specific niche and 'venice music' trigger make it mostly distinct, with only minor overlap risk from the generic 'score' trigger, fitting 'mostly distinct; minor overlap risk' rather than the clearly-niched 5.	4 / 5
	Total	15 / 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-audio-music/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.