test-audio

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and well-sequenced with strong validation checkpoints and recovery loops, and it is lean for its scope. Its main weakness is that a large single-file procedure makes no use of progressive disclosure via reference files.

Suggestions

Split the per-suite assertion specifications (especially Suites 5 and 6) into a references file (e.g., ASSERTIONS.md) linked one level deep from SKILL.md to reduce the inline bulk.

Move the 'Known Issues & Workarounds' section into a separate reference so the main body stays a compact execution overview.

Keep the step/suite sequence inline but summarize each suite's commands in SKILL.md and link to the detail file for the full assertion lists.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable commands and targeted assertions and avoids explaining concepts Claude already knows; even the prose (e.g., one-shot request flags, GLXF composition) is domain-specific knowledge that earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	Every suite provides copy-paste-ready commands with concrete JSON payloads (e.g., `npx iwsdk ecs find --input-json '{"withComponents":["AudioSource"]}'`) plus explicit assertions, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Steps 1–5 are explicitly sequenced with per-suite assertion checkpoints, failure shortcuts ('report FAIL... and skip to Step 5'), and a Recovery feedback loop (stop, restart, retry), matching the 'clear sequence with explicit validation steps; feedback loops' anchor.	3 / 3
Progressive Disclosure	The file is a single ~265-line monolithic procedure; while sections are well-organized, no content is split into one-level-deep references and the under-50-line carve-out does not apply, fitting the 'content that should be separate is inline' anchor rather than the top one.	2 / 3
	Total	11 / 12 Passed

Description

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 specific and distinct, naming concrete audio capabilities and a clear niche, but it omits any explicit 'Use when...' trigger guidance and relies on technical jargon over natural user phrasing.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when testing audio playback, loading, or spatial audio in the IWSDK audio example').

Soften jargon by pairing 'AudioSource' with plain-language terms like 'audio loading' and 'sound playback' that a user would naturally say.

Keep the enumerated capabilities but append a brief trigger clause to lift completeness to the top anchor.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete capabilities — 'AudioSource loading, playback state, stop, spatial audio' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly states what the skill does ('Test audio system...') but provides no 'Use when...' clause or equivalent trigger guidance, so per the guidelines 'when' is missing and completeness is capped at 2.	2 / 3
Trigger Term Quality	It includes some relevant keywords ('audio', 'playback', 'spatial audio') but leans on technical jargon ('AudioSource', 'iwsdk CLI') and lacks common natural variations a user would say, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The scope is tightly bound to testing a specific audio example via the iwsdk CLI, giving it a clear niche unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	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
Commit: 42af866

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