CtrlK
BlogDocsLog inGet started
Tessl Logo

threejs-game-director

Primary entrypoint for complete Three.js browser game creation and premium iteration. Use by default for build-a-game, upgrade, polish, premium, AAA, high-fidelity, showcase, from-scratch, endless runner, arcade, action, or release-ready requests. Orchestrates sibling skills for gameplay, AAA graphics, UI, debug/profile, and QA/release, plus 3D/image/audio generators for characters, vehicles, weapons, buildings, props, skies, textures, logos, icons, GUI art, and SFX/voice. Keeps skill-loading, reference, asset-sourcing, and phase ledgers so users never choose skills manually.

72

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

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with strong workflow gating and clean one-level-deep progressive disclosure backed by real bundle files. The main weaknesses are mild repetition that inflates length and command examples that use unresolved path placeholders rather than copy-paste-ready invocations.

Suggestions

Consolidate the repeated ledger/reference-gate instructions and the multiple citations of references/phase-playbook.md into a single canonical statement to tighten conciseness.

Replace placeholder paths like '<director-skill-dir>' in the bash/python examples with a concrete resolution note (e.g., a one-line variable definition) so commands are closer to copy-paste-ready.

Defer the detailed phase-by-phase routing and premium completion criteria to references/phase-playbook.md, keeping the SKILL.md body to the orchestration overview and phase-entry gates.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence, but the body is dense and repeats the ledger/reference-gate concepts and phase lists across sections (e.g., phase-playbook.md is cited ~6 times and phase routing restated), so it could be tightened.

2 / 3

Actionability

Provides concrete scripts and commands (probe, audit, scaffold, inspect), but the runnable examples carry runtime-resolved placeholders like '<director-skill-dir>' and '<threejs-qa-release-skill-dir>' rather than copy-paste-ready paths, and several sibling-script invocations live outside this bundle.

2 / 3

Workflow Clarity

Clear sequenced phase routing with explicit entry/exit gates, ledgers as validation checkpoints, a credential-probe gate before graphics, and a 'fix or state the blocker instead of claiming completion' feedback loop.

3 / 3

Progressive Disclosure

Overview body is well-organized into sections that point one level deep to real bundle files (references/phase-playbook.md, references/prompt-templates.md, scripts/audit_reference_report.py, scripts/probe_asset_credentials.sh), with sibling references resolved via an explicit path ladder rather than nested indirection.

3 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, trigger-rich, and clearly states both purpose and invocation conditions, with a well-defined niche that distinguishes it from sibling skills. It uses appropriate third-person voice and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists many concrete capabilities — 'orchestrates sibling skills for gameplay, AAA graphics, UI, debug/profile, and QA/release, plus 3D/image/audio generators for characters, vehicles, weapons, buildings, props, skies, textures, logos, icons, GUI art, and SFX/voice' — matching the multi-action anchor.

3 / 3

Completeness

Explicitly answers both 'what' (orchestrates the full Three.js game creation/iteration pipeline) and 'when' via an explicit 'Use by default for...' clause, satisfying the what-AND-when anchor.

3 / 3

Trigger Term Quality

Covers natural phrasing a user would actually say — 'build-a-game, upgrade, polish, premium, AAA, high-fidelity, showcase, from-scratch, endless runner, arcade, action, or release-ready requests' — with strong, varied coverage.

3 / 3

Distinctiveness Conflict Risk

Narrowly scoped to 'Three.js browser game creation and premium iteration' with a distinct orchestrator role over named sibling skills, making false-positive triggering unlikely.

3 / 3

Total

12

/

12

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
majidmanzarpour/threejs-game-skills
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.