CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vrm-mtoon-outline

Adjusting VRM MToon material outline thickness in three-vrm. Covers outline width modes, property access, and how to fix outlines that appear too thick when models are scaled.

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-mtoon-outline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 single-file skill with copy-paste-ready code and useful non-obvious details. Its main weakness is workflow: the batch material modification lacks a post-change validation step and the diagnostic flow is presented after the fix.

Suggestions

Add a verification step after adjusting — e.g., re-run debugOutlineMaterials(vrm) to confirm outlineWidthMode is 'screenCoordinates' and the factor took effect.

Move the Detection Pattern section before the Solution so the diagnose-then-fix sequence reads in order.

Replace the non-English fallback string '未命名' in the debug function with an English placeholder like 'unnamed' for consistency.

DimensionReasoningScore

Conciseness

Mostly lean with tables and only non-obvious notes (the outline-pass material naming, the call-timing warning), but the opening sentence re-states the frontmatter description and the API table partially duplicates the enum block. Not 3: padding is minor and localized; not 5: those small redundancies could be trimmed.

4 / 5

Actionability

Both 'adjustOutlineThickness' and 'debugOutlineMaterials' are complete, executable functions that handle material arrays, check 'isMToonMaterial', and set 'needsUpdate'; the factor-value table gives concrete tuning values covering thin-to-thick cases.

5 / 5

Workflow Clarity

The fix modifies every material in the scene via traverse — a batch operation — with no verification step after applying it (e.g., re-running the debug function to confirm the mode changed), which caps workflow clarity at 3; the Detection Pattern also appears after the Solution, reversing the natural diagnose-then-fix flow. Not 2: the core action is unambiguous and a call-timing checkpoint is given.

3 / 5

Progressive Disclosure

No bundle files exist and the single file is well-sectioned (Symptoms, Key Concepts, Solution, Detection, Notes, API Reference) with a compact inline API table. Not 5: at ~140 lines, the Detection Pattern and API Reference could plausibly be split into reference files; not 3: nothing is buried and structure is clear.

4 / 5

Total

16

/

20

Passed

Description

70%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 distinctive, domain-specific description with concrete actions and natural trigger phrasing, weakened only by the absence of an explicit 'Use when...' clause. Adding one with symptom-based triggers would lift completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when outlines on a VRM model look too thick after scaling, or when outline width needs adjusting at runtime.'

Include common synonyms such as 'outline width' and 'outline too big' to broaden natural trigger coverage.

Mention the screen vs world coordinates distinction, the core fix the skill provides, to sharpen the capability list.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'adjust outline thickness', 'outline width modes', 'property access', 'fix outlines that appear too thick when models are scaled' — but coverage has minor gaps (no mention of screen vs world coordinate modes or runtime adjustment).

4 / 5

Completeness

The 'what' is clear, but there is no 'Use when...' clause or equivalent explicit trigger guidance — the triggering scenario is only embedded inside a capability statement ('how to fix outlines that appear too thick when models are scaled'), which caps completeness at 3.

3 / 5

Trigger Term Quality

Natural phrases like 'outline thickness', 'too thick', 'VRM', 'MToon', and 'scaled' match what a user would actually say, though synonyms such as 'outline width' or 'outline size' are missing.

4 / 5

Distinctiveness Conflict Risk

'VRM MToon material outline thickness in three-vrm' names a clear niche with distinct triggers (VRM, MToon, three-vrm, outline) and virtually no overlap risk with other skills.

5 / 5

Total

16

/

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-mtoon-outline/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.