test-all

Parallel test orchestrator. Runs all 9 test suites concurrently via Task sub-agents and the iwsdk CLI. Handles build, example setup, dev servers, agent launch, polling, retries, and result aggregation.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

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-structured, highly actionable orchestration guide with clear sequencing and validation checkpoints across seven phases. Its only notable weakness is redundancy between the phase descriptions and the 'Key Design Decisions' section.

Suggestions

Trim the 'Key Design Decisions' section to only the points not already covered in the phases, or fold unique insights back into the relevant phases to remove restated material like 'Ports are NOT pre-assigned'.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and tables, but the 'Key Design Decisions' section restates points already made in the phases (e.g. ports not pre-assigned, orchestrator manages servers), adding redundancy that could be tightened.	2 / 3
Actionability	Provides copy-paste-ready commands ('node scripts/test-prep.mjs clone', 'pnpm build:tgz', 'node scripts/test-servers.mjs start') and a concrete sub-agent prompt template with substitution variables.	3 / 3
Workflow Clarity	Seven phases are clearly sequenced with explicit validation checkpoints ('Stop on failure', 60-second readiness check with exit code 1, 20-minute hard timeout) and a retry feedback loop with limits.	3 / 3
Progressive Disclosure	Acts as a clear overview pointing one-level-deep to the 9 per-test skill files (test-interactions/SKILL.md, etc.) and project scripts; detail is appropriately split into those sub-skills rather than inlined here.	3 / 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 actionable, clearly conveying what the orchestrator does across the test lifecycle. Its main weakness is the absence of an explicit 'Use when' trigger and a reliance on technical jargon over natural user phrasing.

Suggestions

Add a 'Use when...' clause stating when Claude should invoke this skill, e.g. 'Use when running the full IWSDK test suite or when the user asks to run all tests.'

Soften technical jargon with natural trigger terms users would actually say, such as 'run all tests' or 'test the IWSDK examples'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'build, example setup, dev servers, agent launch, polling, retries, and result aggregation' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Clearly answers 'what' (runs 9 test suites concurrently, handles the full lifecycle) but has no 'Use when...' trigger clause, capping completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Contains some natural terms ('test suites', 'test') but leans on technical jargon ('Task sub-agents', 'iwsdk CLI', 'polling, retries') and lacks common user phrasings like 'run all tests'.	2 / 3
Distinctiveness Conflict Risk	Names a distinct niche — 'Parallel test orchestrator' for the 9 'iwsdk' test suites — unlikely to conflict with generic skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 10 missing	Warning

	Total	14 / 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.