CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vrm-springbone-physics

Debugging and fixing VRM SpringBone physics issues in three-vrm, including hair/clothing physics that flies upward, sticks out horizontally, or behaves unnaturally.

Quality

78%

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 ./.agent/skills/vrm-physics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable, well-structured diagnostic guide with executable code, prioritized root causes, explicit decision flows, and validation feedback loops. Its main weaknesses are redundancy — the animation loop and collider-reduction code each appear twice, plus speculative padding in Root Cause 2 — and the absence of any reference files for a ~290-line skill.

Suggestions

Remove the duplicated code in "Recommended Initialization Code": the animate loop repeats Root Cause 1's solution and the reduction loop repeats Option 1 — reference the earlier snippets instead.

Cut the speculative "Possible explanations" bullets and the VRChat tangent, and merge Root Cause 2B into Option 5, which already covers scene scaling.

Move the "Key API Reference" and "Joint Settings" tables plus the UniVRM evidence deep-dive into a reference file to slim the main SKILL.md.

DimensionReasoningScore

Conciseness

Mostly high-value domain content with no explanations of concepts Claude already knows, but noticeably loose in places: the animate loop appears in full twice (Root Cause 1 and "Recommended Initialization Code" — "delta = Math.min(delta, 0.05)"), the collider-reduction loop appears in both Option 1 and the init section, and there is speculative padding ("VRoid Studio (most common VRM source) may use consistent internal scaling", the VRChat tangent in Root Cause 2B). This is more than minor over-explanation (ruling out 4) but the padding is structural duplication rather than explained basics (ruling out 2).

3 / 5

Actionability

Fully executable, copy-paste-ready code covers the common cases: THREE.Clock setup with delta clamping ("delta = Math.min(delta, 0.05); vrm.update(delta);"), collider reduction with original-radius preservation ("collider.shape.radius = collider._originalRadius * REDUCTION_FACTOR;"), a complete scaleVRMScene() function, diagnosis snippets ("if (c.shape?.radius) c.shape.radius = 0;"), concrete Unity fix steps, and API/joint settings tables. Only trivial gap: Option 3 uses `colliders` without restating its acquisition, which is shown in adjacent snippets — not enough to drop from anchor 5.

5 / 5

Workflow Clarity

A clear prioritized diagnostic sequence with explicit validation checkpoints and feedback loops: root causes ordered by frequency ("Root Cause 1: Incorrect Delta Time (Most Common - 90%)"), a decision flow ("Only bangs horizontal → Head collider blocking them / All physics horizontal → Gravity direction wrong"), confirmation loops ("If hair now falls correctly, colliders were the issue"), and external validation ("Test with official VRM viewer - if hair is broken there, it's a model issue"). Not 4: validation is explicit for each major branch, not merely present with minor gaps.

5 / 5

Progressive Disclosure

Good structure with well-organized sections and a clearly signaled one-level-deep external reference ("The file format, matching rules, known limitations... are in docs/frontend/vrm.md"), and most content (symptoms, diagnoses, fixes) appropriately lives in the main file. Not 5: no bundle reference files exist and at ~290 lines the "Key API Reference"/"Joint Settings" tables and the UniVRM evidence deep-dive ("#### Confirmed Facts", "#### Empirical Observation") are inline candidates for extraction; not 3: the structure is good and the inline content is mostly where it belongs.

4 / 5

Total

17

/

20

Passed

Description

65%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 precise and distinctive, occupying a clear niche with natural symptom trigger phrases, but it lacks an explicit "Use when..." trigger clause (capping completeness at 3) and describes only generic actions ("Debugging and fixing") rather than the specific fixes the skill delivers. It is solid but leaves triggering to inference from the symptom list.

Suggestions

Add an explicit trigger clause, e.g., "Use when VRM hair or clothing physics misbehaves in three-vrm — hair flying upward on load, sticking out horizontally, or moving unnaturally."

Name one or two concrete remediation actions (e.g., "diagnose delta-time units, adjust SpringBone collider radii") to raise specificity beyond the generic "Debugging and fixing".

Include common user variations such as ".vrm" or "VRoid" to broaden natural trigger-term coverage.

DimensionReasoningScore

Specificity

"Debugging and fixing VRM SpringBone physics issues in three-vrm" names the domain precisely with two actions and concrete symptoms ("flies upward, sticks out horizontally, or behaves unnaturally"), but the verbs are generic and it does not list several specific fix actions (e.g., clamping delta time, reducing collider radii). This matches anchor 3 (domain and 1-2 actions, not comprehensive); it is not 4 because there are not several specific actions, and not 2 because the domain and symptoms are concrete rather than minimal or generic.

3 / 5

Completeness

The "what" is clear ("Debugging and fixing VRM SpringBone physics issues in three-vrm, including hair/clothing physics that..."), but there is no "Use when..." clause or equivalent explicit trigger guidance — the "when" is only weakly implied by the symptom list, which caps completeness at 3 per the guidelines. Not 4 because the when is not explicit; not 2 because the what is specific, not vague.

3 / 5

Trigger Term Quality

Natural phrases a user with this problem would say are present: "hair/clothing physics", "flies upward", "sticks out horizontally", "three-vrm", "SpringBone". A few natural terms are missing (".vrm" file extension, synonyms like "VRoid" or "avatar"), matching anchor 4 rather than 5; it is clearly above anchor 3, which requires missing common variations.

4 / 5

Distinctiveness Conflict Risk

"VRM SpringBone physics issues in three-vrm" defines a clear niche with distinct triggers and minimal conflict risk with other skills. Not 4: there is no meaningful overlap risk — the scope is narrowly pinned to a specific library subsystem.

5 / 5

Total

15

/

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

Project-N-E-K-O/N.E.K.O

Path

.agent/skills/vrm-physics/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.