CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

build-game-camera-controls

Implement or tune Three.js game cameras. Use for isometric framing, follow behavior, orbit/zoom limits, occlusion, lock-on, camera shake, touch camera controls, and camera regression tests.

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

An exceptionally lean, well-structured overview that captures real design wisdom (authoritative target, layered modifiers, gesture-zone separation) and includes a genuine verification checklist. Its main weakness is actionability: the guidance stays at the principle level with no code, parameter values, or concrete testing procedure, so Claude must supply all implementation detail itself.

Suggestions

Add one minimal executable Three.js snippet under Implement — e.g., a damped follow camera with clamped spherical orbit/zoom (position.lerp + THREE.MathUtils.clamp) — so the 'smooth/clamp' bullets have concrete backing.

Make the Verify section actionable: provide a short camera regression-test harness or specific assertions (e.g., 'camera never closer than N units to geometry; player silhouette never occluded for >0.2s') instead of a bare scenario list.

Give the Implement bullets an explicit order (define authoritative target → bounds/zoom limits → occlusion policy → touch zones) and add a recovery hint for failed Verify checks (tune bounds/damping first, then occlusion).

DimensionReasoningScore

Conciseness

The ~120-word body is lean and efficient: no concept explanations Claude already knows (Three.js, reduced motion, occlusion are used without padding), and every bullet adds non-obvious design guidance. Nothing could be cut without losing information.

5 / 5

Actionability

Some concrete guidance exists ("Smooth position and look-at targets independently", "Clamp orbit, pitch, and zoom", "separate camera gesture zones from movement/action controls"), but there is no code, no parameter specifics (damping factors, clamp ranges, shake amplitudes), and several bullets state goals rather than executable steps ("Preserve player, immediate threat, objective, and interaction cues in frame"). This matches 'some concrete guidance but incomplete; missing key details' rather than the code-bearing anchor 4.

3 / 5

Workflow Clarity

A clear Implement → Verify sequence with a real validation checkpoint: the Verify section is an explicit test checklist (corners, tall props, tunnels, lock-on switching, pause, reduced motion, portrait/landscape). Minor gaps remain — the Implement bullets are unordered parallel principles rather than a sequence, and there is no error-recovery loop for failed checks, so it falls short of anchor 5.

4 / 5

Progressive Disclosure

A single-task skill under 50 lines with no need for external references; the content is appropriately self-contained with well-organized sections and no nested or buried references, which earns the top score under the simple-skill guideline.

5 / 5

Total

17

/

20

Passed

Description

92%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 description: concrete, comprehensive capability list paired with an explicit 'Use for' trigger clause, in appropriate imperative/third-person voice. Only minor synonym gaps in trigger terms keep it from a perfect score.

DimensionReasoningScore

Specificity

"Implement or tune" names two concrete actions plus eight enumerated specific capabilities (isometric framing, follow behavior, orbit/zoom limits, occlusion, lock-on, camera shake, touch camera controls, regression tests) — comprehensive coverage of the domain, matching the top anchor rather than the 'minor gaps' anchor.

5 / 5

Completeness

Explicitly answers both: the 'what' is "Implement or tune Three.js game cameras" with enumerated capabilities, and the 'when' is the explicit "Use for..." clause listing concrete trigger scenarios, exactly matching the top anchor.

5 / 5

Trigger Term Quality

Natural phrases users would actually say are present ("camera shake", "lock-on", "follow behavior", "touch camera controls", "orbit/zoom") along with the technology name "Three.js", but a few common variations like "third-person camera", "camera smoothing/lag", or "cinematic camera" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Three.js game cameras) with domain-specific triggers (lock-on, occlusion, camera shake) that are unlikely to fire for unrelated skills; minimal conflict risk.

5 / 5

Total

19

/

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

MengTo/Skills

Path

agent-skills/game-development/build-game-camera-controls/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.