CtrlK
BlogDocsLog inGet started
Tessl Logo

build-hybrid-game-assets

Plan, create, integrate, or audit a hybrid asset pipeline for a Three.js or web game. Use when choosing among imported meshes, procedural 3D geometry, AI-generated reference art, 2D UI media, sprites, VFX, and performance-ready runtime asset delivery.

69

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, opinionated instruction-only skill: dense directive guidance, a decision table up front, and a distinct in-game verification stage. The only gaps are the absence of concrete commands for the performance-measurement step and no explicit error-recovery loop after verification.

DimensionReasoningScore

Conciseness

The body is lean and directive with zero padding — no explanation of what Three.js or asset pipelines are; every line encodes judgment the model lacks (e.g. "Do not force every reference image through image-to-3D reconstruction"), so every token earns its place.

5 / 5

Actionability

Concrete, checkable guidance throughout — "normalize coordinate system, scale, pivot, materials, animation clips, and ownership/license", "expose a factory with named parts, stable sockets, deterministic variation", "Measure representative draw calls, triangles, texture count, and frame time" — but the measurement/verification steps name no commands or tools, leaving minor execution gaps.

4 / 5

Workflow Clarity

A clear pipeline sequence (classify → reference set → build → verify → provenance) with an explicit verification section ("Verify in the game, not the asset viewer") containing measurable checks; it falls short of a 5 only because there is no feedback loop stating what to do when verification fails.

4 / 5

Progressive Disclosure

The skill is 37 lines with no bundle files and no need for external references; it is well organized with a classification table and clear section headers, so under the simple-skill guidance it matches the well-organized-sections anchor.

5 / 5

Total

18

/

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 with an explicit what/when structure and a specific, natural-sounding trigger list covering the asset-representation decision space. Its only weaknesses are lifecycle-generic action verbs and a few missing synonymous trigger terms.

DimensionReasoningScore

Specificity

"Plan, create, integrate, or audit" lists several concrete actions tied to a specific domain ("hybrid asset pipeline for a Three.js or web game") with a rich enumeration of asset types, but the verbs are lifecycle-generic rather than operationally distinct like "extract/merge/convert", so minor coverage gaps remain versus the comprehensive anchor.

4 / 5

Completeness

Both halves are explicit: the "what" ("Plan, create, integrate, or audit a hybrid asset pipeline for a Three.js or web game") and a concrete "Use when..." clause enumerating the decision contexts, matching the anchor that clearly and explicitly answers both what and when.

5 / 5

Trigger Term Quality

Natural trigger terms are well covered — "Three.js", "web game", "imported meshes", "procedural 3D geometry", "sprites", "VFX", "AI-generated reference art" — but a few common variations users would say (e.g. "3D models", "textures", "game art") are missing.

4 / 5

Distinctiveness Conflict Risk

"Hybrid asset pipeline for a Three.js or web game" carves a clear niche with distinct triggers (sprites, VFX, procedural geometry), but there is minor overlap risk with closely related general game-development or 3D-asset skills, keeping it just below the minimal-conflict anchor.

4 / 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
MengTo/Skills
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.