CtrlK
BlogDocsLog inGet started
Tessl Logo

game-audio

Game audio principles. Sound design, music integration, adaptive audio systems.

48

Quality

51%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/game-development/game-audio/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 body is a well-structured, dense reference of game-audio decision tables, but it is conceptual knowledge without executable implementation guidance or a sequenced workflow, keeping actionability and workflow clarity mid-range.

Suggestions

Add at least one concrete, executable example (e.g., a middleware config snippet or FMOD/Wwise event setup) to lift actionability.

Convert one section into a short worked workflow with sequenced steps so the skill can be followed end-to-end.

Trim widely-known audio fundamentals (basic reverb/EQ/format explanations) and keep only the game-specific decision rules to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is dense reference tables with little prose padding, but much of it (mix dB levels, 3D distance falloff, file formats) is general audio knowledge Claude already knows, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.

3 / 5

Actionability

Provides concrete decision frameworks (crossfade vs stinger, dB levels, format picks) but no executable code, middleware commands, or API hooks, so guidance is concrete but incomplete for an instruction skill.

3 / 5

Workflow Clarity

There is no multi-step process to sequence — the skill is a reference rather than a workflow — and while content is organized into sections, there is no sequenced procedure or validation checkpoints.

3 / 5

Progressive Disclosure

Content over 50 lines is well-organized into eight numbered sections with consistent tables and clear headers; no external references are needed for this self-contained reference, matching the 'good structure' anchor.

4 / 5

Total

13

/

20

Passed

Description

48%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 identifies its niche and relevant trigger terms but lists topic areas rather than concrete actions and omits any 'Use when' trigger guidance, which caps completeness and specificity.

Suggestions

Add a 'Use when...' clause naming concrete triggers (e.g., 'Use when designing or integrating game sound, music states, or adaptive audio systems').

Reword topic nouns as concrete actions (e.g., 'Design sound effects, integrate music states, configure adaptive audio').

Include common synonyms users might say (e.g., 'SFX', 'footsteps', 'BGM', 'mixing') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Game audio principles') and lists topic areas ('Sound design, music integration, adaptive audio systems'), but these are nouns/topics rather than concrete actions, matching the anchor for minimal or generic actions.

2 / 5

Completeness

Provides a clear 'what' (game audio principles across sound design, music, adaptive systems) but has no 'Use when...' trigger clause; per guidelines a missing trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user might say ('game audio', 'sound design', 'music integration') but lacks common synonyms and variations, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Game audio' is a clear niche with minimal conflict risk, with only minor overlap against a general music/audio skill, matching the 'mostly distinct' anchor.

4 / 5

Total

12

/

20

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
vudovn/ag-kit
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.