CtrlK
BlogDocsLog inGet started
Tessl Logo

ammo-mmd-physics-hacks

应对 WebGL 端 MMD 物理 (Ammo.js) 炸模、穿模、卡顿等极限边缘工况的终极调优指南与 Hack 技巧。

52

Quality

57%

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/ammo-mmd-physics-hacks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and dense with concrete parameter values, but it relies on metaphor-laden prose over executable code and omits verification feedback loops for the iterative tuning it describes.

Suggestions

Add at least one executable code snippet (e.g. a velocity-limiter loop or MotionState sync call) so the guidance is copy-paste ready rather than prose-only.

Trim colorful metaphors ('超音速抛出', '降维打击', '幽灵穿模') to reduce token cost without losing the technical point.

Add a brief validation step for each fix (e.g. 'replay the VMD at 2× speed and confirm no tearing before moving on') to create feedback loops for the iterative tuning.

DimensionReasoningScore

Conciseness

It assumes Claude knows the domain with no basic-concept padding, but the metaphor-heavy prose ("毁灭性的原形复原能力", "超音速抛出", "降维打击") adds tokens without instructional value and could be tightened.

2 / 3

Actionability

Provides concrete API calls and specific parameter values (setActivationState(4), LinearVelocity >50.0, ERP 0.8, CFM 0.015) but presents them as prose with no executable code blocks, so guidance is concrete yet not copy-paste ready.

2 / 3

Workflow Clarity

Six root-cause→solution pairs are clearly numbered, but there are no validation/verification steps or test feedback loops for iterative physics tuning, which caps workflow clarity at 2.

2 / 3

Progressive Disclosure

A compact single-purpose skill under 50 lines with no external references, organized into clear sections (症状, 根本原因与解决方案, 关键经验), which satisfies progressive disclosure for a simple skill.

3 / 3

Total

9

/

12

Passed

Description

57%

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 names a clear, distinctive niche and surfaces relevant symptom terms, but it stops short of listing concrete actions and lacks any explicit "Use when..." trigger guidance.

Suggestions

Add a concrete action list (e.g. 'fixes model tearing, clipping, and frame drops by tuning Ammo.js rigid bodies, joints, and velocity limits') instead of the abstract '终极调优指南与 Hack 技巧'.

Append an explicit trigger clause such as 'Use when MMD physics causes 炸模, 穿模, or 卡顿 in WebGL/Ammo.js scenes.'

Include natural term variations users might say (e.g. 'MMD 物理炸模', '衣服穿模', 'Ammo 物理 lag') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain (WebGL MMD physics / Ammo.js) and symptom categories (炸模/穿模/卡顿), but the actions are abstract ("终极调优指南与 Hack 技巧") rather than enumerating multiple concrete operations.

2 / 3

Completeness

Answers "what" (tuning guide for MMD physics edge cases) but has no explicit "Use when..." trigger clause; the "when" is only weakly implied by the symptom list, which caps completeness at 2.

2 / 3

Trigger Term Quality

Includes some natural terms a developer would say ("MMD 物理", "Ammo.js", "炸模", "卡顿"), but leans heavily on technical jargon ("极限边缘工况", "Hack 技巧") and lacks common variations.

2 / 3

Distinctiveness Conflict Risk

The niche is highly specific (WebGL MMD physics via Ammo.js) with distinct triggers, making it unlikely to fire for the wrong skill.

3 / 3

Total

9

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Project-N-E-K-O/N.E.K.O
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.