CtrlK
BlogDocsLog inGet started
Tessl Logo

game-audio

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

49

Quality

53%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/game-development/game-audio/SKILL.md

The canonical home for this skill is game-audio in administrakt0r/AI-Agents-Safe-Coding-Skills

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-organized reference of game-audio decision tables, but it is descriptive rather than instructional: no executable guidance, no multi-step workflow with validation, and some basic-concept padding. Its strongest dimension is structure.

Suggestions

Trim basic-concept explanations (category definitions, distance behavior) that Claude already knows to improve conciseness.

Add at least one concrete, actionable worked example (e.g. a mix-level setup or an adaptive-music transition config) to lift actionability.

If a destructive/batch audio workflow (e.g. batch encoding, asset replacement) is intended, add explicit validation checkpoints to raise workflow clarity.

DimensionReasoningScore

Conciseness

The body is compact and table-driven, but several tables explain basic concepts Claude already knows (what Music/SFX/Ambient categories are, near/far distance behavior), and the closing '50% of the game experience is audio' line is filler, fitting 'mostly efficient but includes some unnecessary explanation.'

3 / 5

Actionability

Concrete decision support exists (specific dB levels, MB budgets, platform formats), but the body only describes and references rather than instructing — there are no executable steps, commands, or code, so it sits at 'some concrete guidance but incomplete.'

3 / 5

Workflow Clarity

Content is organized into clear numbered sections, but there is no multi-step workflow with validation checkpoints; it is reference material, matching 'steps listed but validation gaps; sequence present but checkpoints missing.'

3 / 5

Progressive Disclosure

No bundle files exist, but the single SKILL.md is well-structured into eight clearly headed sections with appropriately placed reference content; it is monolithic rather than split, keeping it just below 5.

4 / 5

Total

13

/

20

Passed

Description

53%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 is specific and on-domain but reads as a topic list rather than an action-oriented trigger. Its main weakness is the absence of any 'Use when...' guidance, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when implementing game sound effects, adaptive music, or 3D audio for games.'

Reframe the topic list as concrete actions ('Design', 'Integrate', 'Configure') to lift specificity above 3.

Include natural synonyms users say (SFX, Foley, interactive/adaptive music) to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Game audio principles') and three specific sub-areas ('Sound design, music integration, adaptive audio systems'), but lists topics rather than concrete actions a user would invoke, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor.

3 / 5

Completeness

It gives a clear 'what' (audio principles across sound design, music, adaptive systems) but lacks any 'Use when...' clause, so per the judging guideline a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like 'Game audio' and 'Sound design' are present, but common variations/synonyms (e.g. SFX, Foley, interactive music) are missing, fitting 'some relevant keywords but missing common variations or synonyms.'

3 / 5

Distinctiveness Conflict Risk

'Game audio' is a clear, distinct niche with minimal overlap risk against generic skills, though the absence of explicit trigger phrases keeps it just below a 5.

4 / 5

Total

13

/

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.

Validation — 15 / 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
administrakt0r/AI-Agents-Safe-Coding-Skills
Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/game-development/game-audio/SKILL.md

Commit

57c135b

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill