add-mouse-driven-orbit

Add restrained mouse-driven orbit and parallax depth to a Three.js hero by damping one pointer target and splitting it across camera translation, look-at, and small object rotations. Use for passive cinematic 3D heroes, pointer-responsive scenes, organic model parallax, and interactive depth where OrbitControls would feel like a product viewer.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 high-quality, actionable body with concrete code, a landed-values table, and a thorough verification checklist. Its main weakness is progressive disclosure: the closing references to demo/index.html and demo/PROMPT.md point at files that are not present in the skill bundle.

Suggestions

Add the referenced demo/index.html and demo/PROMPT.md files to a demo/ directory, or remove the two links in the final 'Verify' section so no signaled reference is missing.

If keeping the demo files out of the bundle, replace the links with an inline minimal reproduce snippet so the 'working proof' is self-contained.

Consider an explicit 'If the corners clip or the subject slides, reduce the translation/look-at coefficients and re-check' feedback loop to lift workflow clarity from a checklist to validate→fix→retry.

Dimension	Reasoning	Score
Conciseness	Lean and dense throughout — specific constants (0.055, -26, +16, 42%), complete code blocks, and a values table, with no padding about Three.js or basic concepts Claude already knows; every section delivers task-specific craft.	5 / 5
Actionability	Fully executable, copy-paste-ready code for the pointer handler, frame-loop damping, settled-value publishing, and the camera/object transform split, plus a concrete landed-values table covering the common cases.	5 / 5
Workflow Clarity	A clear phased sequence (record → dampen → split → preserve framing → lifecycle → verify) with an explicit 8-point Verify checklist, but no validate→fix→retry feedback loop, which keeps it just below 5.	4 / 5
Progressive Disclosure	The body is well-sectioned, but it ends by pointing to [demo/index.html](demo/index.html) and [demo/PROMPT.md](demo/PROMPT.md) as the 'working proof', and no demo/ directory (nor references/, scripts/, assets/) exists — the signaled references are dangling.	3 / 5
	Total	17 / 20 Passed

Description

87%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 both the mechanism and the use cases, and sharply distinguishes itself from direct-manipulation alternatives. It is concise without fluff and avoids over-claims.

Dimension	Reasoning	Score
Specificity	Names several concrete actions — 'damping one pointer target', 'splitting it across camera translation, look-at, and small object rotations', 'parallax depth' — with only minor breadth gaps, matching the 'lists several specific actions' anchor rather than the fully comprehensive 5.	4 / 5
Completeness	Explicitly answers both what ('Add restrained mouse-driven orbit and parallax depth... by damping... and splitting it across...') and when ('Use for passive cinematic 3D heroes, pointer-responsive scenes, organic model parallax, and interactive depth where OrbitControls would feel like a product viewer') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage including natural developer terms ('Three.js hero', 'mouse-driven orbit', 'parallax depth', 'pointer-responsive', 'OrbitControls') with synonyms, though a few common phrasings like 'camera parallax' or '3D tilt' are absent.	4 / 5
Distinctiveness Conflict Risk	Clear niche — passive cinematic 3D-hero depth — explicitly contrasted against OrbitControls ('would feel like a product viewer'), giving distinct triggers and minimal conflict risk with adjacent camera-control skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: MengTo/Skills
Path: agent-skills/web-design/add-mouse-driven-orbit/SKILL.md
Commit: 321c769

Reviewed: 11 hours ago

Table of Contents

Discovery Implementation Validation

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.