CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

3d-camera-interaction

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

Quality

77%

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

67%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 well-organized troubleshooting skill with a tight symptom-cause-fix structure and genuinely non-obvious domain knowledge (pixel-to-world scaling at variable camera distance). Its main weakness is that the boundary-detection solution is left as pseudocode stubs where the actual correction logic should be, preventing copy-paste readiness.

Suggestions

Complete the boundary-detection code: materialize the 8 bounding-box corners (e.g., box.min/max combinations), the min/max update inside the forEach, and the actual pull-back math inside 'if (visiblePixels < MIN_VISIBLE_PIXELS)' so the fix is copy-paste executable.

Remove the '关键公式' section's duplication of the worldHeight/pixelToWorld code already shown in cause 1, keeping only the world-to-screen projection snippet that is new.

Add a brief verification step (e.g., how to confirm drag stays pixel-synced after zoom, or how to test the visible-pixels threshold) to close the workflow loop.

DimensionReasoningScore

Conciseness

The body is efficient: it goes straight to symptoms, root causes, and fixes with no padding on concepts Claude already knows, and the '为什么发生' explanations cover non-obvious camera-projection reasoning. Score 4 rather than 5 because the '关键公式' section repeats code already shown and the emoji '关键经验' section could be trimmed.

4 / 5

Actionability

The pixel-to-world fix (cause 1) is complete, executable code, but the boundary fix (cause 2) contains placeholders: 'const corners = [/* 8个顶点 */]', '// 更新边界...', and the correction body is just '// 将模型拉回可见区域'. Core steps being stubs rather than executable code matches anchor 3; it is above anchor 2 because half the guidance is concrete and runnable.

3 / 5

Workflow Clarity

Each fix follows a clear symptom → root cause → solution sequence, and the boundary solution is explicitly numbered (compute box projection, compute visible area, correct only when too small) with a conditional correction checkpoint. Not score 5 because there is no verification step for confirming the fix works; not score 3 because the sequences are well-defined and the correction condition acts as a checkpoint.

4 / 5

Progressive Disclosure

The skill is a single self-contained file with no bundle directories, organized under clear sections (症状, 根本原因, 关键公式, 关键经验) that are easy to navigate. It scores 4 rather than 5 because the body exceeds the ~50-line simple-skill threshold and includes some repetition between the solution code and the formulas section.

4 / 5

Total

15

/

20

Passed

Description

75%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, specific description that clearly states what the skill does and conveys when to use it through concrete symptom descriptions. Third-person voice and natural trigger terms are present; the main improvement would be an explicit 'Use when...' clause and a few more synonyms (pan/平移, camera).

DimensionReasoningScore

Specificity

The description lists several concrete actions ('处理 3D 模型拖拽、缩放、边界检测') and names the specific problems solved ('鼠标移动与模型移动不同步、缩放后只能看到模型一部分'). It stops short of score 5 because coverage has minor gaps (e.g., no mention of pan or camera-distance correction), but it goes beyond the 1-2 actions of score 3.

4 / 5

Completeness

The 'what' is clear (correct methods for dragging, zooming, and boundary detection in Three.js) and the 'when' is given explicitly through the symptom clause ('解决鼠标移动与模型移动不同步...只能看到模型一部分等问题'), which functions as trigger guidance. Not score 5 because the 'when' is symptom-implicit rather than a concrete 'Use when...' phrase; not score 3 because the trigger guidance is explicit, not merely implied.

4 / 5

Trigger Term Quality

Natural keywords users would say are present: 'Three.js', '3D 模型', '拖拽', '缩放', '边界检测'. A few common variations are missing (e.g., '平移'/'pan', 'camera', 'orbit controls'), which keeps it below the comprehensive synonym coverage of score 5.

4 / 5

Distinctiveness Conflict Risk

The description is pinned to a clear niche (Three.js 3D model drag/zoom/boundary interaction bugs) with distinct symptom-based triggers, giving minimal conflict risk. It sits at 4 rather than 5 only because a closely related general Three.js or camera-control skill could still overlap.

4 / 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/3d-interaction/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.