CtrlK
BlogDocsLog inGet started
Tessl Logo

audio-jingle

Audio generation skill — jingles, beds, voiceover, and sound effects. Routes music requests to Suno V5 / Udio / Lyria, speech to MiniMax TTS / FishAudio / ElevenLabs V3, and SFX to ElevenLabs SFX or AudioCraft. Output is one MP3/WAV file saved to the project folder.

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, highly actionable, and clearly sequenced with a proof-before-dispatch checkpoint. Its only notable weakness is progressive disclosure: the resource map and frontmatter reference example.html, which is not actually present in the bundle.

Suggestions

Either add the missing example.html to the bundle or remove it from the resource map and the frontmatter preview entry so referenced paths are real.

If example.html is intentionally optional, note that in the resource map (e.g. '(optional preview)') so the listing matches the actual bundle structure.

DimensionReasoningScore

Conciseness

Lean and efficient — a compact sub-mode table, terse numbered steps, and only genuinely non-obvious domain notes (MiniMax voice_id specifics); no padding or explanations of concepts Claude already knows.

3 / 3

Actionability

Provides a fully executable dispatcher command with concrete flags, real parameter bindings, and a specific example voice id ('male-qn-qingse') — copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

Clear Step 0→4 sequence with an explicit verification checkpoint ('Proof it before dispatching — even one stray comma changes the cadence') and concrete duration/structure rules; audio generation is not a destructive batch op, so no validate-retry loop is required.

3 / 3

Progressive Disclosure

Sections are well-organized, but the resource map lists 'example.html' (also referenced as the preview entry) and that file does not exist on disk — a dead one-level reference is a real navigation flaw rather than a clean 3.

2 / 3

Total

11

/

12

Passed

Description

82%

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, third-person, and well-targeted to a clear audio niche, but omits an explicit 'Use when...' trigger clause, capping completeness. Trigger terms live in the separate triggers field rather than the description prose.

Suggestions

Add an explicit 'Use when...' clause to the description (e.g. 'Use when the user needs a jingle, background bed, voiceover, or sound effect') so completeness can reach 3.

Fold one or two of the most natural trigger phrases (e.g. 'sound effect', 'voiceover') into the description prose itself rather than relying solely on the triggers field.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Routes music requests to Suno V5 / Udio / Lyria, speech to MiniMax TTS / FishAudio / ElevenLabs V3, and SFX to ElevenLabs SFX or AudioCraft' plus 'Output is one MP3/WAV file saved to the project folder' — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly answers 'what' (audio generation routed to named models, one output file) but has no 'Use when...' clause or explicit trigger guidance in the description, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

Includes natural terms a user would say — 'jingles, beds, voiceover, and sound effects', 'music', 'speech' — giving good coverage rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

The audio-generation niche (jingles, beds, voiceover, SFX routed to specific audio models) is distinct and unlikely to trigger for non-audio skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
Reviewed

Table of Contents

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.