test-audio

Test audio system (AudioSource loading, playback state, stop, spatial audio) against the audio example using the iwsdk CLI.

Quality

80%

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/test-audio/SKILL.md

Quality

Content

92%Weight 40%Scale 1-3

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 tight, highly actionable test playbook with strong sequencing and recovery loops. Its only weakness is progressive disclosure: all detail lives inline in one file rather than being split into referenced materials.

Suggestions

Move the six suite specs and/or Known Issues into referenced files (e.g., references/suites.md) to shorten the overview and aid navigation.

If keeping inline, add a brief table of contents at the top so the six suites are discoverable at a glance.

Dimension	Reasoning	Score
Conciseness	Lean and command-driven; every line earns its place (assertions, CLI calls, one-line pitfalls like 'Strings silently fail to coerce') without explaining concepts Claude already knows.	3 / 3
Actionability	Fully executable `npx iwsdk ...` commands with concrete JSON payloads and explicit per-test assertions — copy-paste ready.	3 / 3
Workflow Clarity	Clear Step 1–5 sequence with validation checkpoints (connectivity check, error-log asserts), a Recovery feedback loop, and a retry policy for transient failures.	3 / 3
Progressive Disclosure	Well-organized into sections, but everything (six suite specs, known issues) is inline in a single ~270-line file with no bundle references; content that could be split out is not.	2 / 3
	Total	11 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 well-scoped to a distinct audio-testing niche, but omits an explicit 'Use when' trigger clause and leans on internal jargon over natural user phrasing.

Suggestions

Add an explicit trigger clause, e.g. 'Use when testing the audio example's AudioSource loading, playback, stop, or spatial audio behavior.'

Soften jargon by including natural user terms like 'sound' or 'play audio' alongside 'AudioSource'.

Consider noting when not to use it (e.g., non-audio examples) to further reduce conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'AudioSource loading, playback state, stop, spatial audio' — naming specific capabilities rather than vague language.	3 / 3
Completeness	Clearly answers 'what' the skill does, but lacks an explicit 'Use when...' trigger clause; the 'when' is only implied by the argument-hint, capping completeness at 2 per guidelines.	2 / 3
Trigger Term Quality	Contains relevant terms ('Test audio system', 'playback', 'stop', 'spatial audio') but leans on technical jargon ('AudioSource', 'iwsdk CLI') and misses common user phrasings like 'play audio' or 'sound'.	2 / 3
Distinctiveness Conflict Risk	Scoped to 'the audio example using the iwsdk CLI', a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: facebook/immersive-web-sdk
Path: .claude/skills/test-audio/SKILL.md
Commit: 0fb2195

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