iwsdk-planner

IWSDK experience pipeline and planning guide. Use when building a new IWSDK app/game end-to-end, planning new IWSDK features, designing systems/components, reviewing IWSDK code architecture, or when the user asks about IWSDK patterns, ECS design, signals, or reactive programming. Runs a phased ideation → design → grounding → architecture → build → verify → ship pipeline, orchestrating sub-agents per phase where the harness supports them.

Quality

100%

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

Quality

Content

100%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.

A well-architected orchestration skill: lean per-phase, highly actionable with real commands, explicit gated sequencing with validation feedback loops, and exemplary one-level-deep progressive disclosure via a reference table whose files all exist.

Dimension	Reasoning	Score
Conciseness	The body is dense with IWSDK-specific process knowledge Claude would not already know (phase gates, CLI commands, fallback ladders) and avoids explaining basic concepts like ECS or reactive programming; every section earns its tokens despite the length, which is justified by a 7-phase pipeline.	3 / 3
Actionability	Provides concrete executable commands throughout ('npx iwsdk status', 'npx iwsdk reference warmup', 'npx tsc --noEmit', 'npm run build', 'npx gh-pages -d dist'), exact file paths, specific CLI query verbs, and concrete priority bands (0–9 input / 10–19 sim / 20–29 visual sync / 30+ UI).	3 / 3
Workflow Clarity	Phases 0–7 are explicitly sequenced with a gate after each phase, a persistent state file (design/PIPELINE.md), and feedback loops ('debug with the runtime tools... not by staring at code', 'Fix and re-run failures'), plus an autonomous-mode stop-after-2-3-cycles rule for stubborn criteria.	3 / 3
Progressive Disclosure	SKILL.md is a clear overview with a 'Reference Files' table giving a 'Load when' column for each of the six one-level-deep references, all of which exist (api-reference, ideation, design-deck, grounding, build-milestones, verification); detail is appropriately split out rather than inlined.	3 / 3
	Total	12 / 12 Passed

Description

100%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.

A specific, well-triggered, third-person description that clearly states both what the skill does and when to use it, with a distinct IWSDK niche. Voice is correctly third person ('Runs a phased... pipeline'), so no specificity penalty applies.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'building a new IWSDK app/game end-to-end, planning new IWSDK features, designing systems/components, reviewing IWSDK code architecture' — and names the phased pipeline it runs, matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what ('IWSDK experience pipeline and planning guide... Runs a phased ideation → design → grounding → architecture → build → verify → ship pipeline') and when ('Use when building... or when the user asks about...'), with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Covers natural trigger phrasing a IWSDK developer would say ('building a new IWSDK app/game', 'planning new IWSDK features', 'reviewing IWSDK code architecture', 'IWSDK patterns, ECS design, signals, or reactive programming'), giving good coverage rather than just a single keyword.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to IWSDK with distinct triggers (ECS, signals, reactive programming, IWSDK app/game), making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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: 1 missing	Warning

	Total	14 / 16 Passed

Repository: facebook/immersive-web-sdk
Path: .claude/skills/iwsdk-planner/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.