threejs-game-director

Entrypoint for building, upgrading, and finishing Three.js browser games. Routes work across the sibling threejs-* skills for gameplay, graphics, UI, 3D/image/audio asset generation, debugging, and release. Use for build-a-game, upgrade, polish, premium, AAA, high-fidelity, showcase, from-scratch, endless runner, arcade, action, and release-ready requests.

Quality

93%

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 well-structured director skill that stays lean by delegating depth to siblings and three real reference files, with concrete commands and a sequenced build flow including validation checkpoints. The main gap is dependency on placeholder-resolved sibling-skill scripts for full copy-paste readiness.

Suggestions

Add a short numbered 'build sequence' checklist with explicit validate->fix->retry steps for the core loop so the workflow reads as a crisp procedure rather than prose.

Provide a one-line example of resolving `<director-skill-dir>` to a concrete path (e.g. an echo/expand snippet) so the example commands are copy-paste ready without rereading the sibling-resolution section.

Note explicitly which sibling-skill scripts (create_threejs_game.py, inspect-threejs-canvas.mjs) are required at runtime and where they live, so a missing sibling is detected before the command fails.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence (no explanation of what Three.js, a HUD, or a shader is) and delegates detail to sibling skills and references, so nearly every line carries operational rule rather than padding.	5 / 5
Actionability	It gives concrete executable commands (probe_asset_credentials.sh, create_threejs_game.py, inspect-threejs-canvas.mjs with full flags, check_evidence.py) and specific thresholds ('no category below 2 and an average of at least 2.3'), but relies on resolved placeholders and sibling-skill scripts not in this bundle, leaving a minor copy-paste gap.	4 / 5
Workflow Clarity	The build is clearly sequenced (design brief -> core loop -> asset jobs -> assess playable scene -> multiply content -> verification) with checkpoints ('Inspect concepts and generated model previews before their dependent generation', 'Repeat checks only after relevant changes'), though the flow is prose rather than a crisp validate->fix->retry checklist.	4 / 5
Progressive Disclosure	SKILL.md acts as a true overview/entrypoint pointing one level deep to references that all exist (asset-recovery.md, evidence-manifest.md, workflow-evaluations.md) and to sibling skills via a clear table, with well-signaled 'Read ... when ...' navigation.	5 / 5
	Total	18 / 20 Passed

Description

100%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, third-person description that clearly answers what and when with concrete actions and a rich set of natural trigger terms. Minimal conflict risk thanks to the specific Three.js-game niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('building, upgrading, and finishing Three.js browser games', 'Routes work across the sibling threejs-* skills for gameplay, graphics, UI, 3D/image/audio asset generation, debugging, and release') with comprehensive coverage of the sub-domains.	5 / 5
Completeness	It explicitly states both what it does (entrypoint that routes work across sibling skills) and when to use it via a concrete 'Use for ...' clause with multiple trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	The 'Use for' clause enumerates natural phrases users would actually say ('build-a-game, upgrade, polish, premium, AAA, high-fidelity, showcase, from-scratch, endless runner, arcade, action, and release-ready'), covering synonyms and variations comprehensively.	5 / 5
Distinctiveness Conflict Risk	The 'Three.js browser games' niche and director-routing role are clearly distinct from generic skills, with triggers specific enough to avoid firing for unrelated game or non-game requests.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: majidmanzarpour/threejs-game-skills
Path: skills/threejs-game-director/SKILL.md
Commit: e5f301d

Reviewed: 3 days 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.