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

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.

An exemplary router skill: lean, fully actionable, with clear sequencing and explicit routing tie-breakers, delegating all implementation detail to one of two well-signaled playbooks. The only structural weakness is the orphaned references/api-reference.md, which no file in the skill's navigation points to.

DimensionReasoningScore

Conciseness

The ~35-line router body contains zero concept explanation and no padding; every line is a routing rule or handoff constraint (e.g. "A detailed acceptance contract does not turn a greenfield build into an iteration"). It fully assumes Claude's competence and every token earns its place.

5 / 5

Actionability

Guidance is fully executable for an instruction-only router: exact file paths (references/planner.md, references/iterate.md), a numbered 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 absence of code is appropriate per the instruction-only scoring note.

5 / 5

Workflow Clarity

The routing decision has explicit disambiguation checkpoints ("Observable workspace state wins over wording" plus four tie-breaker bullets), and the handoff is a clear 4-step sequence including stating the route aloud before loading. No destructive or batch operations exist, so no validation cap applies; the single routing action is unambiguous.

5 / 5

Progressive Disclosure

The body is an ideal thin overview pointing to exactly two real, clearly signaled playbook files (both verified to exist) that are loaded one at a time. However, bundle inspection shows references/api-reference.md (1532 lines) is referenced nowhere in SKILL.md or the playbooks, leaving a large file undiscoverable through navigation — a minor organization gap that keeps this below the 5 anchor.

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.

The description is concise, concrete, and fully answers both what the skill does and when to invoke it, with an explicit trigger clause and a distinct IWSDK niche. Trigger-term coverage is good but could add a few more natural user phrasings for build/change requests.

DimensionReasoningScore

Specificity

"Routes fresh builds to an internal planning playbook and bounded changes to an established app to an internal iteration playbook" lists several concrete routing actions for the named IWSDK domain. Not 3 because more than 1-2 specific actions are stated; not 5 because coverage is confined to routing and says nothing about what the skill provides beyond dispatch.

4 / 5

Completeness

The what is explicit ("Routes fresh builds to an internal planning playbook and bounded changes... to an internal iteration playbook") and the when is explicit with a concrete trigger phrase ("Invoke first for every IWSDK implementation request"). Both questions are clearly and explicitly answered, matching the 5 anchor.

5 / 5

Trigger Term Quality

Natural phrases a user would say are present: "IWSDK development", "IWSDK implementation request", "fresh builds", "changes to an established app". A few natural variations (e.g. "new experience", "fix", "edit") are missing, keeping it below the comprehensive-anchor at 5.

4 / 5

Distinctiveness Conflict Risk

"Single entry point for IWSDK development" carves out a clear niche around a distinct named SDK with explicit entry-point claims, so conflict risk with other skills is minimal. Not 4 because no overlapping skill domain is identifiable from the description itself.

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

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