CtrlK
BlogDocsLog inGet started
Tessl Logo

game-audio

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

52

Quality

58%

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/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

68%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 lean, well-structured reference of game-audio decisions with concrete numbers and examples, scoring well on conciseness, actionability, and organization. Its main weakness is the absence of any sequenced workflow with validation checkpoints, and the trailing 'When to Use' boilerplate adds little value.

DimensionReasoningScore

Conciseness

The body is dense, domain-specific reference data in tables (priority hierarchy, dB mix levels, formats, memory budgets) that mostly earns its tokens; only the closing motivational quote and the generic boilerplate 'When to Use' line are trimmable padding, matching the score-4 'efficient; minor instances of over-explanation' anchor.

4 / 5

Actionability

It gives concrete, applicable decisions (3-5 variations per sound, specific dB ranges per category, per-platform formats, a gunshot attack/body/tail/sweetener layering example); as an instruction-only skill the absence of code is not penalized, but it stops short of fully copy-paste-ready guidance, so score 4 rather than 5.

4 / 5

Workflow Clarity

There is no real procedural workflow to sequence; the music state diagram (menu -> exploration -> combat -> victory) is a flow but lacks any validation checkpoints, fitting the score-3 'sequence present but checkpoints missing' anchor rather than 4.

3 / 5

Progressive Disclosure

Content is well-organized into eight clearly headed sections with no nested references and a self-contained single-file structure appropriate for a reference skill; it falls short of 5 only because no quick-start/advanced split or external references are used to offload detail.

4 / 5

Total

15

/

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 a distinct niche (game audio) and lists relevant sub-domains, but it reads as a topic list rather than a statement of concrete actions and omits any 'Use when...' trigger guidance. Adding action verbs and an explicit trigger clause would raise specificity and completeness.

Suggestions

Rewrite as concrete actions, e.g. 'Designs game sound effects, integrates adaptive music systems, and mixes 3D audio for game engines.'

Add an explicit 'Use when...' clause, e.g. 'Use when designing or implementing game audio, SFX, adaptive music, or spatial/3D sound.'

Include common synonyms users actually say (SFX, mixing, dialogue, Foley, 3D audio) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Game audio principles') and sub-areas ('Sound design, music integration, adaptive audio systems') but uses only noun-phrase topics with no concrete action verbs, matching the score-2 anchor ('Processes PDF files') rather than the action-listing score-3 anchor.

2 / 5

Completeness

The 'what' (the game-audio domain and its sub-areas) is clear, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Contains several natural terms a developer would say ('game audio', 'sound design', 'music integration', 'adaptive audio') but misses common synonyms and variations (SFX, mixing, Foley, dialogue, 3D audio), fitting the score-3 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Game audio' is a distinct, well-bounded niche unlikely to trigger for unrelated skills, with only minor overlap risk against general audio/music skills; it falls short of 5 only because explicit trigger phrases are absent.

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

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