CtrlK
BlogDocsLog inGet started
Tessl Logo

3d-camera-interaction

Three.js 中处理 3D 模型拖拽、缩放、边界检测的正确方法。解决鼠标移动与模型移动不同步、缩放后只能看到模型一部分等问题。

62

Quality

72%

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/3d-interaction/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is well-organized, concise, and largely actionable, with concrete code for both root causes and a clear diagnostic structure. The main gaps are a placeholder in the bounding-box solution and the absence of explicit verification steps.

Suggestions

Replace the '/* 8个顶点 */' placeholder with executable corner derivation from box.min/box.max so the clamping solution is fully copy-paste ready.

Add a short validation step after each fix (e.g. 'Confirm cursor-to-model movement is now 1:1 at all zoom levels') to strengthen workflow clarity.

Fill in the '// 更新边界...' comment with the actual min/max update logic to remove the remaining pseudocode gap.

DimensionReasoningScore

Conciseness

Lean symptom→cause→fix structure with executable code and no padding about basic concepts Claude already knows; the '为什么发生' explanations are relevant but slightly trimmable, fitting 'efficient; minor instances of over-explanation'; not 5 because those explanatory passages could be tightened.

4 / 5

Actionability

Provides concrete, mostly copy-paste-ready code for dynamic pixel-to-world mapping and Box3-based visible-pixel clamping; not 5 because the second solution contains placeholders ('/* 8个顶点 */', '// 更新边界...') instead of fully executable corner derivation.

4 / 5

Workflow Clarity

Clear diagnostic flow (症状 → 原因 → 解决方案) with both root causes paired to fixes and a formulas/takeaways summary; not 5 because there are no explicit validation checkpoints (e.g. 'verify drag is now 1:1 with the cursor') to confirm each fix worked.

4 / 5

Progressive Disclosure

Self-contained body with well-organized sections (症状, 根本原因, 关键公式, 关键经验) and no nested references; no bundle files exist to verify, and at ~110 lines it exceeds the under-50-line simple-skill threshold, so it sits at 'good structure; minor organization gaps' rather than 5.

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.

The description is specific and well-targeted to a distinct Three.js niche with natural symptom-based trigger terms, but it lacks an explicit 'Use when...' clause, which caps its completeness. Adding an explicit trigger sentence would raise the completeness score.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when 3D model dragging feels out of sync with the mouse or when zoomed-in models cannot be panned fully into view.'

Include common synonyms/file or library cues (e.g. 'Three.js OrbitControls pan', 'VRM/Live2D camera') to broaden natural trigger coverage.

Lead with the concrete actions before the problem statement to sharpen the 'what does this do' answer.

DimensionReasoningScore

Specificity

Names the Three.js domain plus several concrete actions (拖拽、缩放、边界检测) and two specific problems, fitting 'lists several specific actions; minor gaps in coverage'; not 5 because coverage is not comprehensive and the framing '处理...的正确方法' is slightly generic.

4 / 5

Completeness

Has a clear 'what' (handling drag/zoom/boundary detection) but no explicit 'Use when...' trigger clause, so per the missing-trigger guidance completeness is capped at 3; the '解决...问题' phrasing only weakly implies 'when'.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('Three.js', '3D 模型', '拖拽', '缩放') plus symptom phrases like '鼠标移动与模型移动不同步' and '缩放后只能看到模型一部分', giving good keyword coverage; not 5 because synonyms and extension variants are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Three.js 3D model camera interaction) with distinct symptom-based triggers and minimal overlap with other skills; fits the 'clear niche with distinct triggers; minimal conflict risk' anchor.

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.

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.