CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

threejs-loaders

Three.js asset loading - GLTF, textures, images, models, async patterns. Use when loading 3D models, textures, HDR environments, or managing loading progress.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/threejs-loaders/SKILL.md

The canonical home for this skill is threejs-loaders in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is highly actionable — executable, current examples covering every major loader, compression option, and error-recovery pattern — and cleanly sectioned. Its weaknesses are length-driven: substantial duplicated boilerplate and a monolithic single-file layout where per-format and advanced details belong in one-level-deep reference files.

Suggestions

Move per-format and compression details (OBJ/FBX/STL/PLY, Draco/KTX2/Meshopt setup, caching, alternate sources) into a references/ file such as references/formats.md, keeping SKILL.md as a concise overview with clearly signaled one-level-deep links.

Remove duplicated snippets: basic TextureLoader/GLTFLoader usage already shown in Quick Start is repeated verbatim in later sections, and the three near-identical promise wrappers (loadGLTF/loadRGBE/loadTexture) can be one parameterized helper.

Trim tutorial-style comments that restate defaults or enumerate every option (filter list, wrapping options) — keep only non-obvious gotchas like 'onProgress not supported for image loading'.

DimensionReasoningScore

Conciseness

The body is code-dense and largely avoids explaining basic concepts in prose, but at ~640 lines it carries notable duplication: basic TextureLoader/GLTFLoader usage appears in Quick Start and again verbatim in later sections, three near-identical promise wrappers (loadGLTF/loadRGBE/loadTexture), and tutorial-style comments restating defaults ("NearestFilter - pixelated", "Default" next to filters). This fits anchor 3 (mostly efficient but could be tightened) better than anchor 4, whose over-explanation is only minor, and better than anchor 2, since no paragraphs are spent teaching concepts Claude already knows.

3 / 5

Actionability

Nearly every section is copy-paste-ready executable JavaScript covering the common cases: GLTF with Draco/KTX2/Meshopt, OBJ+MTL/FBX/STL/PLY, promisified loading, Promise.all over multiple assets, THREE.Cache, a full AssetManager class, blob/data-URL/ArrayBuffer sources, and fallback/retry/timeout patterns. This matches anchor 5 (fully executable, specific examples cover common cases); nothing drops to pseudocode or vague direction.

5 / 5

Workflow Clarity

As a topical reference rather than a linear procedure, the sections are clearly organized and the Error Handling section supplies explicit feedback loops (fallback, retry with backoff, timeout via AbortController) for the one fragile operation — network loading. It sits at anchor 4 rather than 5 because there are no explicit validation checkpoints (e.g., verifying assets are ready in onLoad before removing the placeholder or starting the scene), and below-4 anchors' "steps missing/incoherent" and "sequence with validation absent" do not apply given the structure and error-recovery patterns present.

4 / 5

Progressive Disclosure

Section headers are clear and consistent, but there are no bundle files at all — the entire API reference (per-format loaders, compression setup, caching, source handling) is inlined in one ~640-line SKILL.md. This matches anchor 3 (good structure, but content that should be separate is inline, no references) rather than anchor 2, whose "minimal structure / no section headers" does not describe this well-organized file, and rather than anchor 4, which requires most bulk content appropriately placed in separate files.

3 / 5

Total

15

/

20

Passed

Description

83%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 that explicitly states both what the skill does and when to use it, in third person, using natural trigger phrases with no fluff or over-claims. The only improvement space is broader trigger coverage (file extensions like .glb, and non-GLTF format names) and slightly more action variety in the capability list.

DimensionReasoningScore

Specificity

"Three.js asset loading - GLTF, textures, images, models, async patterns" names the domain and enumerates a broad set of concrete capability areas, but the only explicit action is "loading" — the objects are specific while the actions are implied rather than multiple distinct stated actions. This sits above anchor 3 (only 1-2 concrete actions) but below anchor 5 (multiple specific concrete actions), so it fits anchor 4: several specifics with minor gaps.

4 / 5

Completeness

Both questions are answered explicitly: what — "Three.js asset loading - GLTF, textures, images, models, async patterns"; when — "Use when loading 3D models, textures, HDR environments, or managing loading progress" with concrete trigger phrases. This mirrors anchor 5's example structure; it is above anchor 4 only in that the "when" clause is already fully explicit and concrete, not merely present.

5 / 5

Trigger Term Quality

Natural user phrases like "loading 3D models", "textures", "HDR environments", and "managing loading progress" are present alongside the technical term GLTF. A few common variations are missing (file extensions like .glb/.gltf, "skybox", other formats like FBX/OBJ), which matches anchor 4 (good coverage, a few natural terms missing) rather than anchor 5's comprehensive synonym and extension coverage.

4 / 5

Distinctiveness Conflict Risk

The Three.js loader niche is clear with distinct triggers (GLTF, HDR environments, loading progress), but the skill's own "See Also" points to related skills (threejs-textures, threejs-materials) whose scope overlaps with texture loading and material handling here. That is minor overlap with closely related skills — anchor 4 — rather than the minimal-conflict, fully distinct niche of anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (646 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 3 missing, 1 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/threejs-loaders/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.