test-audio
Test audio system (AudioSource loading, playback state, stop, spatial audio) against the audio example using the iwsdk CLI.
61
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/test-audio/SKILL.mdQuality
Discovery
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.
The description is technically specific and clearly identifies concrete actions and tools, making it distinctive. However, it lacks an explicit 'Use when...' clause, which limits completeness, and the trigger terms are heavily technical jargon that users may not naturally use when requesting this skill.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to test or verify audio functionality, sound playback, or spatial audio features in the iwsdk project.'
Include more natural trigger terms such as 'sound', 'audio test', 'play audio', 'test sound system' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: AudioSource loading, playback state, stop, spatial audio testing, and mentions the specific tool (iwsdk CLI) and testing against an audio example. | 3 / 3 |
Completeness | Clearly answers 'what' (test audio system components against the audio example using iwsdk CLI), but lacks an explicit 'Use when...' clause or equivalent trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'AudioSource', 'playback', 'spatial audio', 'iwsdk CLI', but these are fairly domain-specific. Missing common user-facing variations like 'sound', 'audio test', 'play sound'. Users might not naturally say 'AudioSource loading' or 'iwsdk CLI'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: testing audio systems with the iwsdk CLI against an audio example. The combination of AudioSource, spatial audio, and iwsdk CLI makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted test procedure skill with excellent actionability and workflow clarity. Every command is concrete and executable, assertions are specific with expected values, and the workflow includes proper validation checkpoints, error recovery, and cleanup. The main weaknesses are some redundancy in warnings/known issues and the monolithic structure that could benefit from splitting reference material into separate files.
Suggestions
Consolidate the three separate warnings about JSON booleans into a single prominent note at the top, removing the duplicates from Known Issues and the IMPORTANT callout.
Consider moving the 'Known Issues & Workarounds' and 'Component Schema' details into separate reference files to reduce the main skill's length and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete commands and assertions, but the 'Known Issues & Workarounds' section is somewhat verbose and repeats information already stated inline (e.g., boolean values warning appears three times, the one-shot flag behavior is explained both in Suite 2 and in Known Issues). Some explanatory text could be trimmed. | 2 / 3 |
Actionability | Every step provides exact CLI commands with specific arguments, concrete assertion criteria with expected values, and clear pass/fail conditions. Commands are copy-paste ready with only entity index substitution needed. The output format and parsing expectations are well-defined. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced from installation through cleanup with explicit validation checkpoints (connectivity verification in Step 3, pre-test setup assertions, per-suite assertions). Recovery procedures with retry logic are well-defined, and there's a clear feedback loop for server startup failures and transient errors. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file at ~200 lines. While internally well-structured with clear headers and numbered suites, the Known Issues section and the detailed component schema could potentially be split into reference files. However, no bundle files exist to support this, and for a test procedure skill, keeping everything in one file is somewhat justified. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- facebook/immersive-web-sdk
- Commit
3a08b40
- 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.