CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

iwsdk-dev

Single entry point for IWSDK development. Invoke first for every IWSDK implementation request. Routes fresh builds to an internal planning playbook and bounded changes to an established app to an internal iteration playbook.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is iwsdk-dev in facebook/immersive-web-sdk

SKILL.md
Quality
Evals
Security

Quality

Content

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

A model router skill: concise, decisive, and fully executable, with unambiguous routing criteria and a disciplined handoff. The only weakness is in the surrounding bundle rather than the file itself — a large orphaned reference file and a second level of nesting.

Suggestions

Reference references/api-reference.md from the playbook (or playbooks) that needs it — it is currently 60KB of content no file points to, making it undiscoverable.

Consider surfacing the second-level reference (references/headless-rendering.md) as a clearly labeled 'deep dive' in the playbook so the nesting depth is explicit to the reader.

Add a one-line note in the handoff section that deeper references (headless rendering, API reference) exist so Claude knows the full bundle map without reading them.

DimensionReasoningScore

Conciseness

The ~40-line body is lean with no filler: every line does routing work ('Route the current request before inspecting files, planning, invoking a specialist, or editing code'), and the disambiguation bullets ('Observable workspace state wins over wording') are substantive rules rather than padding. It assumes Claude's competence and never explains concepts Claude already knows.

5 / 5

Actionability

Fully actionable for an instruction-only skill: exact file paths ('planner path: references/planner.md'), a concrete handoff sequence, and explicit prohibitions ('Do not read project files, call Bash, create a plan, or invoke a specialist between this router and the selected playbook'). The routing criteria are decidable from observable workspace state, so nothing is left abstract.

5 / 5

Workflow Clarity

The routing task is simple and single-purpose, and per the simple-skills note it scores 5 when the single action is unambiguous — here the decision procedure includes explicit precedence rules ('Observable workspace state wins over wording', 'explicit user selection of a child route overrides automatic routing') and a guarded handoff ('Never load the other playbook later, including after context compaction'). No destructive or batch operations exist, so the validation cap does not apply.

5 / 5

Progressive Disclosure

The entry point itself is exemplary — a router with well-signaled one-level references (planner.md, iterate.md) and 'load exactly one playbook' discipline. Scored against the actual bundle, though: references/api-reference.md (60KB) is never referenced by SKILL.md or either playbook (orphaned and undiscoverable), and the playbooks add a second reference level (references/headless-rendering.md), so navigation to part of the bundle is broken. Not 5 because content is not appropriately split across the whole bundle; not 3 because the entry file's own structure and signaling are strong and references that exist are clearly signaled.

4 / 5

Total

19

/

20

Passed

Description

87%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 description: it explicitly answers both what and when, uses concrete routing actions in third-person voice, and carves out a distinct niche with low conflict risk. Only minor upside remains from adding a few more natural trigger synonyms.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions: 'Invoke first for every IWSDK implementation request', 'Routes fresh builds to an internal planning playbook and bounded changes to an established app to an internal iteration playbook'. Not 5 because the capabilities the playbooks themselves cover are delegated rather than enumerated; not 3 because well more than 1–2 specific actions are stated.

4 / 5

Completeness

Both questions answered explicitly: what = 'Single entry point for IWSDK development... Routes fresh builds... and bounded changes...'; when = 'Invoke first for every IWSDK implementation request' — a concrete, explicit trigger clause. Uses third-person voice throughout ('Routes'), per the guidelines.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'IWSDK development', 'implementation request', 'fresh builds', 'bounded changes', 'established app' — phrasings users would plausibly say. A few natural variations that appear in the body ('new experience', 'scaffold', 'fix', 'extend', 'tune') are missing from the description, which keeps it at 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

'IWSDK development' is a clear, distinct niche and 'Single entry point... Invoke first' frames it as the sole trigger for that namespace, minimizing conflict risk with any non-IWSDK skill.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

packages/core/agent-guidance/claude/.claude/skills/iwsdk-dev/SKILL.md

Reviewed

Table of Contents

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.