team-audio

Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

Quality

76%

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 ./.claude/skills/team-audio/SKILL.md

Quality

Content

85%

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

A well-structured, actionable orchestration skill with clear sequencing and validation checkpoints, undermined only by some redundancy between the delegation overview and the per-step agent detail.

Suggestions

Consolidate the "How to Delegate" section with the per-Step agent lists to remove the overlap where each agent's responsibility is stated twice.

Reconcile the agent roster: the description and delegation list omit accessibility-specialist, yet it is spawned in Step 2 — list it consistently everywhere.

Dimension	Reasoning	Score
Conciseness	The body is directive and avoids explaining concepts Claude already knows, but the "How to Delegate" section previews each agent's responsibility and the later Steps re-list those same agents in full, so it could be tightened.	2 / 3
Actionability	It gives concrete executable orchestration guidance: named subagent_types, per-agent task bullet lists, specific file paths (design/audio/audio-[feature].md, design/gdd/sound-bible.md), and exact validation questions for the engine specialist.	3 / 3
Workflow Clarity	It provides a clear Phase 0 → steps 1–6 sequence with explicit checkpoints (AskUserQuestion approval gates), a Verdict COMPLETE/BLOCKED system, and an Error Recovery Protocol feedback loop for blocked agents.	3 / 3
Progressive Disclosure	The skill is self-contained with no bundle files and is organized into clear sections (Phase 0, How to Delegate, Steps, File Write Protocol, Next Steps, Error Recovery); for a self-contained skill, well-organized sections satisfy progressive disclosure.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 concrete, distinct description that names the team composition and pipeline scope, but it omits an explicit "Use when..." trigger clause and lacks common natural-language variations users might say.

Suggestions

Append a "Use when..." clause naming natural triggers, e.g. "Use when designing game audio for a feature or area (combat, menus, biomes, boss encounters)."

Add common trigger terms users would actually say, such as "music", "SFX", "sound design", and "game audio", to broaden natural-keyword coverage.

Reflect the full pipeline scope (accessibility, technical implementation, code integration) that the body actually covers, so the description is not understated.

Dimension	Reasoning	Score
Specificity	The description names four concrete team roles ("audio-director + sound-designer + technical-artist + gameplay-programmer") and a concrete two-stage pipeline "from direction to implementation", listing multiple specific concrete elements rather than vague language.	3 / 3
Completeness	It clearly answers "what" (orchestrate an audio team through a full pipeline) but provides no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	It includes relevant terms like "audio team", "audio-director", and "sound-designer" a user might say, but misses common variations such as "music", "SFX", "game audio", or "sound design" as trigger phrases.	2 / 3
Distinctiveness Conflict Risk	It carves a clear niche — game audio team orchestration from direction to implementation — with distinct audio-centric triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: Donchitos/Claude-Code-Game-Studios
Path: .claude/skills/team-audio/SKILL.md
Commit: 984023d

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.