test-level

Test level system (LevelRoot, LevelTag, authored environment, scene hierarchy) against the poke example using the iwsdk CLI.

Quality

75%

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-level/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 highly actionable, well-sequenced test procedure with strong validation and recovery loops; its only weakness is monolithic inline content with no progressive disclosure via referenced files.

Dimension	Reasoning	Score
Conciseness	The body is operationally dense — concrete commands and assertions with minimal prose — and its explanatory sentences (e.g. LevelSystem identity enforcement, Entity 0 wrapping the Three.js Scene) convey codebase-specific behavior Claude does not already know, so they earn their place rather than padding.	3 / 3
Actionability	It provides fully executable, copy-paste-ready `npx iwsdk ...` commands with explicit JSON inputs and concrete per-command assertions, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	A clear five-step sequence with explicit validation checkpoints (connectivity check, pre-test log assertion, per-suite assertions) and a Recovery feedback loop (stop, restart, re-run setup, retry once per suite) matches the level-3 anchor.	3 / 3
Progressive Disclosure	Sections are well-organized, but the skill is a ~238-line monolithic SKILL.md with no bundle files or one-level-deep references; at this length, detail such as per-suite assertions or Known Issues could be externalized, fitting the 'content that should be separate is inline' anchor.	2 / 3
	Total	11 / 12 Passed

Description

57%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 clearly scoped to a distinct niche, but it answers only the "what" and lacks an explicit "Use when..." trigger clause plus broader natural-language triggers.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when verifying the poke example's level system after changes to LevelRoot, LevelTag, authored environment, or scene hierarchy.' to raise completeness to 3.

Broaden trigger terms with natural user phrasing such as 'level system tests', 'scene hierarchy checks', or 'poke example regression' beyond internal class names.

Name multiple concrete actions (e.g. 'Run, assert, and report on...') instead of the single verb 'Test' to lift specificity.

Dimension	Reasoning	Score
Specificity	It names the domain (level system) and several concrete targets (LevelRoot, LevelTag, authored environment, scene hierarchy) against a specific example, but relies on a single action verb ("Test") rather than listing multiple concrete actions, so it sits at the "names domain and some actions" anchor rather than the multi-action level 3.	2 / 3
Completeness	It clearly answers "what" (test the level system against the poke example via iwsdk CLI) but provides no "Use when..." or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant keywords exist ("test level system", "poke example", "iwsdk CLI"), but the natural-language coverage leans on internal class names (LevelRoot, LevelTag) and lacks common user-facing variations, matching the "some relevant keywords but missing common variations" anchor.	2 / 3
Distinctiveness Conflict Risk	The description is tightly scoped to a specific project (poke example, iwsdk CLI, LevelRoot/LevelTag), giving it a clear niche with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	9 / 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-level/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.