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.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./design-templates/audio-jingle/SKILL.md

Quality

Content

76%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.

An actionable, well-structured skill body with a copy-paste-ready dispatcher and compact sub-mode routing. Its main weakness is workflow clarity: it dispatches and hands off without any verify-the-output checkpoint.

Suggestions

Add a verification step after dispatch, e.g. "Confirm the returned file rendered in the FileViewer transport controls; if absent, re-run the dispatcher."

Signal the example.html bundle file with purpose, e.g. "See example.html for a rendered preview-card sample" rather than only listing it in the resource map.

Tighten the Step 0 metadata-branching paragraph — the inference-vs-clarifying-form guidance can be trimmed without losing the key rule.

Dimension	Reasoning	Score
Conciseness	Lean and efficient — the sub-mode table compresses model routing, the workflow is terse, and the voice_id guidance covers genuinely non-obvious behavior; a couple of sentences (e.g. the metadata-branching paragraph) could tighten further.	4 / 5
Actionability	Provides a fully executable copy-paste dispatcher command with every flag, the exact JSON output shape, concrete per-sub-mode plan bullets, and a named example voice_id (`male-qn-qingse`) covering the common cases.	5 / 5
Workflow Clarity	A clear numbered sequence (Step 0–4) with branching logic, but no validation/verification checkpoint — the skill dispatches and reports without confirming the file landed or rendered correctly.	3 / 5
Progressive Disclosure	Good structure: overview table, a resource map listing the single bundle file (`example.html`), and sectioned workflow with no nested references; the example.html reference is listed but not clearly signaled with its purpose.	4 / 5
	Total	16 / 20 Passed

Description

71%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.

A specific, well-scoped audio-generation description with concrete actions and provider routing, weakened only by the absence of an explicit "Use when…" trigger clause. It reads as third-person and avoids fluff, but does not tell Claude precisely when to invoke it.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user requests music, jingles, voiceover, TTS, or sound effects / SFX."

Include common synonyms in the trigger phrasing — "audio", "soundtrack", and the abbreviation "SFX" — to broaden natural-term coverage.

Clarify the output artifact in the trigger clause ("…and a single MP3/WAV file should be saved to the project") so the when-condition is concrete.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across distinct categories — "jingles, beds, voiceover, and sound effects" — with explicit model routing per category (Suno V5/Udio/Lyria, MiniMax TTS/FishAudio/ElevenLabs V3, ElevenLabs SFX/AudioCraft).	5 / 5
Completeness	Has a clear "what" (routes requests to named providers, outputs one MP3/WAV) but no explicit "Use when…" clause — the "when" is only weakly implied, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural user terms ("music", "jingle", "voiceover", "sound effect") but omits common synonyms like "audio", "soundtrack", or the "SFX" abbreviation.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear audio-generation niche with named providers, giving minimal conflict risk; held at 4 rather than 5 because the lack of an explicit trigger clause leaves the niche edge slightly soft.	4 / 5
	Total	16 / 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: design-templates/audio-jingle/SKILL.md
Commit: 1a7a23d

Reviewed: about 4 hours 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.