audio-track-production

End-to-end audio production workflow with stems, effects, archiving, and verification

Quality

55%

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 ./benchmarks/gdpval/skills/audio-track-production/SKILL.md

Quality

Content

55%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 skill delivers a well-sequenced, validated audio-production workflow with mostly executable code, but it is markedly verbose (duplicated full-workflow example) and monolithic, with no bundle files or progressive disclosure despite content that would benefit from separation.

Suggestions

Remove the 'Complete Workflow Example' section or collapse it into the per-step code, since it duplicates Steps 3-7 and roughly doubles the body length.

Move reusable functions (generate_stem, apply_lowpass_filter, apply_reverb_simple, export_audio, verify_outputs) into scripts/ files and reference them from SKILL.md to improve progressive disclosure.

Replace placeholder lines like '# Replace with actual mix' and the undefined 'stem_audio' variable with concrete, runnable code so the examples are fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose, repeating near-identical code across the per-step sections and a full 'Complete Workflow Example' that duplicates Steps 3-7, plus explanatory comments ('Example: 440Hz tone', 'Replace with actual synthesis') that pad token usage.	2 / 5
Actionability	Most guidance is executable Python with concrete function definitions and specific parameters (48000 Hz, FLOAT subtype, 137s), though the mix step uses placeholder comments ('Replace with actual mix') and undefined variables (stem_audio), leaving minor gaps.	4 / 5
Workflow Clarity	The seven-step pipeline is explicitly sequenced with verification at Step 1, per-export asserts in Step 5, archive verification in Step 6, and a final verification step with an assert feedback loop, satisfying the validation-checkpoint anchor.	5 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent) yet the body inlines ~270 lines of code that would clearly benefit from being split into separate reference scripts, with no section signaling or one-level-deep references.	2 / 5
	Total	13 / 20 Passed

Description

56%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 clearly conveys what the skill does across a concrete production pipeline, but it omits any explicit 'Use when' trigger guidance and is light on natural trigger synonyms, which cap completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to produce, mix, or master a track, generate stems, or deliver verified audio archives.'

Include natural trigger terms and file extensions users would actually say, such as 'mixing', 'mastering', 'exporting stems', '.wav', and 'multi-track'.

Tighten the action list to more specific verbs (e.g. 'generate stems, apply DSP effects, export master and stems, archive deliverables, verify specs').

Dimension	Reasoning	Score
Specificity	Names the audio-production domain and several concrete actions ('stems, effects, archiving, and verification'), but the actions are high-level categories rather than fully enumerated, leaving minor coverage gaps.	4 / 5
Completeness	It clearly answers 'what' (end-to-end audio production with stems, effects, archiving, verification) but provides no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	'audio production workflow', 'stems', 'effects', 'archiving' are relevant domain terms but it lacks common natural phrasings (e.g. 'mixing', 'mastering', 'exporting stems', '.wav') users would actually say when requesting this skill.	3 / 5
Distinctiveness Conflict Risk	The combination of 'stems', 'effects', 'archiving', and 'verification' carves a fairly distinct niche with only minor overlap risk against generic audio/media skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: HKUDS/OpenSpace
Path: benchmarks/gdpval/skills/audio-track-production/SKILL.md
Commit: 3827781

Reviewed: 13 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.