CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

iwsdk-build-model

Build or materially repair one reusable IWSDK 3D model as a glTF or deterministic parentless Three.js Object3D, including geometry, surface-relative detail, materials, semantic hierarchy, isolated inspection, and focused refinement. Does not arrange scenes, lighting, environment, or cameras; use iwsdk-compose-scene for those.

Quality

85%

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-build-model in facebook/immersive-web-sdk

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 exceptionally actionable, well-sequenced workflow where nearly every line encodes project- or tool-specific knowledge Claude could not infer, with strong validation gates and bounded iteration loops. The main improvement opportunities are tightening a few repetitive passages and moving select reference material out of the always-loaded body.

DimensionReasoningScore

Conciseness

The body is dense and almost entirely non-derivable, project-specific guidance (IWSDK realms, manifest rules, surface-frame contracts, tool transport limits), rewarding it over verbose examples that re-explain known concepts. Minor instances could be trimmed — e.g. repeated clay-form admonitions ("Do not use tertiary detail to hide unresolved primary geometry" vs. "Do not answer a merely sparse-looking render by multiplying tertiary greebles") and the long Claude Code tool-mechanics passage — so it fits "efficient with minor over-explanation" rather than the every-token-earns-its-place level of a 5.

4 / 5

Actionability

Guidance is fully executable: copy-paste bash for locating and installing the bundled library, exact `npx @iwsdk/cli asset render-preview` commands with JSON payloads, a complete TypeScript API signature list with parameter shapes (`{z, halfW, hUp, hDown?, cx?, cy?, power?}`), and concrete recovery steps (`browser_reload_page`). This matches the copy-paste-ready anchor covering the common cases; a 4 would imply missing key details, which are not present.

5 / 5

Workflow Clarity

A clear six-phase sequence (define contract, choose representation, build large-to-small, validate, review/refine, hand off) with explicit validation checkpoints and feedback loops: the typecheck gate before `iwsdk dev up`, material and clay preview passes, a seven-item review checklist, bounded correction rounds with rerun instructions, and defined stop conditions. This matches the anchor for clear sequencing, explicit validation, and error-recovery loops; a 4 would require minor checkpoint gaps, which are not evident.

5 / 5

Progressive Disclosure

The single bundle file (assets/hardsurface.ts.template) is referenced one level deep via a clear copy command, and its ~35-line public API surface is deliberately inlined so the implementation never needs reading — a coherent structure. It stays at 4 rather than 5 because the body is one long (~310 line) file where some content, such as the CLI preview reference or the construction-library conventions, could be split into separate reference files to shorten the always-loaded overview.

4 / 5

Total

18

/

20

Passed

Description

75%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 specific, well-scoped description with concrete capabilities and excellent boundary routing against sibling skills. Its main weakness is the absence of an explicit "Use when..." trigger clause, leaving the activation conditions implied rather than stated.

Suggestions

Add an explicit trigger clause, e.g. "Use when building, repairing, or refining a single 3D model, mesh, or glTF asset; for scene layout, lighting, or cameras use iwsdk-compose-scene instead."

Include natural user synonyms and file extensions such as "mesh", "procedural asset", and ".gltf" to broaden trigger-term coverage.

State positively when the skill applies (e.g. "Use when a scene needs a new or materially changed model") rather than only describing what it does not own.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions and deliverables — "Build or materially repair one reusable IWSDK 3D model", "geometry, surface-relative detail, materials, semantic hierarchy, isolated inspection, and focused refinement" — giving comprehensive coverage of the skill's capabilities with no vague filler. It matches the anchor for multiple specific concrete actions; a 4 would require minor gaps in coverage, which are not evident.

5 / 5

Completeness

The "what" is clear and detailed, but there is no "Use when..." clause or equivalent positive trigger guidance; the negative boundary "Does not arrange scenes, lighting, environment, or cameras; use iwsdk-compose-scene for those" only weakly implies when this skill applies. Per the judging guideline, a missing explicit trigger clause caps completeness at 3 even with a strong "what"; it does not reach 4 because the "when" is never affirmatively stated.

3 / 5

Trigger Term Quality

Natural terms users would say are present — "3D model", "build", "repair", "glTF", "Three.js" — but common variations such as "mesh", "asset", "procedural model", or file extensions like ".gltf" are missing. This fits "Good keyword coverage; a few natural terms missing" rather than the comprehensive synonym/extension coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (single IWSDK model construction) and explicitly routes neighboring work elsewhere ("use iwsdk-compose-scene" for scenes, lighting, cameras, environment), giving minimal conflict risk with closely related skills. This is a direct match for the clear-niche anchor; a 4 would require unresolved minor overlap, which the explicit routing eliminates.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

facebook/immersive-web-sdk

Path

packages/core/agent-guidance/claude/.claude/skills/iwsdk-build-model/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.