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

85%

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

77%Weight 40%Scale 1-5

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

An excellently structured multi-phase pipeline skill with explicit gates, validation feedback loops, and clean progressive disclosure through verified reference files. Its main weakness is conciseness — several operational rules repeat across phases and could be consolidated.

Suggestions

Consolidate recurring rules (nested-scaffold prohibition, dev-server ownership, iwsdk CLI status/warmup handling) into a single canonical 'Operating Principles' or Phase-0 statement, then reference it from later phases instead of restating it.

Inline the core @iwsdk/create scaffold flag set (or a compact example command) in the Scaffold Checkpoint so the most common build step is executable without opening a reference.

Trim the duplicated warmup/status instructions across Phase 0, the Scaffold Checkpoint, and Phase 3 to a single decision flow.

Dimension	Reasoning	Score
Conciseness	The ~365-line body is dense and largely free of beginner-concept padding, but several rules recur across phases ('never scaffold a nested app', 'main agent owns the dev server', iwsdk CLI status/warmup guidance) and could be tightened to a single canonical statement.	3 / 5
Actionability	Concrete executable commands appear throughout (npx iwsdk status/reference warmup, npx tsc --noEmit, npm run build, npx gh-pages -d dist, ecs query/snapshot/diff) with named file paths and assertion patterns; the only gap is that exact @iwsdk/create scaffold flags are deferred to a reference rather than inlined.	4 / 5
Workflow Clarity	Phases 0–7 are explicitly numbered, each with a Goal, procedure, and explicit Gate, plus a PIPELINE.md state file with status table, milestone log, resuming rules, and fix-and-rerun feedback loops — matching the level-5 anchor with validation checkpoints and error recovery.	5 / 5
Progressive Disclosure	The body is a clear orchestrator overview that signals one-level-deep references via a well-organized 'Reference Files' table (file + 'Load when') and per-phase 'Playbook:' citations; all six referenced files exist on disk and content is appropriately split.	5 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

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 strong, specific description with an explicit 'Use when' trigger clause and comprehensive concrete actions scoped to the distinct IWSDK domain. It is slightly jargon-heavy in its trigger terms, keeping trigger_term_quality just below the top anchor.

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') plus a full enumerated phased pipeline — comprehensive coverage matching the level-5 anchor.	5 / 5
Completeness	Explicitly answers both 'what' (a phased ideation→ship planning pipeline orchestrating sub-agents) and 'when' via a concrete 'Use when building... planning... designing... reviewing... or when the user asks about...' trigger clause.	5 / 5
Trigger Term Quality	Good natural-term coverage ('building a new IWSDK app/game', 'planning new IWSDK features', 'IWSDK patterns'), but leans on technical jargon ('ECS design, signals, reactive programming') and misses a few common lay variations, sitting above the level-3 anchor but short of fully comprehensive level-5.	4 / 5
Distinctiveness Conflict Risk	Carves a clear IWSDK-specific niche with distinct triggers (IWSDK app/game, ECS design, signals, reactive programming) and minimal overlap risk with unrelated skills.	5 / 5
	Total	19 / 20 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: 13f42e7

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