threejs-debug-profiler

Debug and profile Three.js browser games: blank canvases, render and runtime bugs, asset and audio loading, animation, resize, mobile input, plus performance profiling of draw calls, triangles, textures, memory, shader and post-processing cost, and bundle size.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/threejs-debug-profiler/SKILL.md

Quality

Content

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

The body is a lean, well-structured triage and profiling playbook with explicit validation checkpoints and a cleanly signaled one-level-deep reference. The only weaknesses are a slightly verbose opening meta-paragraph and measurement mechanics delegated to the reference rather than named inline.

Suggestions

Tighten the opening paragraph about verification scope — it reads as process meta-guidance that could be shortened without losing meaning.

Name the concrete measurement method inline in the Profile section (e.g. renderer.info fields or DevTools) rather than only delegating to the playbook.

Keep the numbered Debug/Profile checklists and the single clearly-signaled reference — this structure is well done.

Dimension	Reasoning	Score
Conciseness	The body is dense and lean with no concept explanations, but the opening meta-paragraph about reusing the lead's reproduction and when broader testing is warranted is slightly over-explained and could be trimmed.	4 / 5
Actionability	Concrete, specific triage checks ('Check canvas display size against drawing-buffer size', 'Check renderer, context, and loop ownership') are highly actionable, but exact measurement mechanics and commands are delegated to the reference rather than given inline, leaving minor gaps.	4 / 5
Workflow Clarity	Debug (8 numbered steps) and Profile (5 numbered steps) are clearly sequenced with explicit validation checkpoints — 'retest the exact broken path' and 'Re-measure the same scenario and confirm visuals and playability held' — providing feedback loops.	5 / 5
Progressive Disclosure	A clear overview (Reference, Debug, Profile, Report) points to one well-signaled, one-level-deep reference (references/debug-playbook.md, verified to exist) with appropriate content split and easy navigation.	5 / 5
	Total	18 / 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.

The description is specific, distinctive, and rich in domain keywords, but it omits any explicit 'Use when...' trigger guidance, which caps completeness at 3. Adding a trigger clause naming common user complaints (FPS, lag, frame rate) would lift both completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when a Three.js game shows a blank canvas, runtime errors, broken loading, or low FPS / lag.'

Include natural complaint phrasings users actually say ('low FPS', 'frame rate', 'lag', 'stutter') alongside the technical perf terms.

Keep the current specific capability list — it is comprehensive and distinctive.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities — 'blank canvases, render and runtime bugs, asset and audio loading, animation, resize, mobile input, plus performance profiling of draw calls, triangles, textures, memory, shader and post-processing cost, and bundle size' — giving comprehensive coverage rather than just a few actions.	5 / 5
Completeness	The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Strong natural keywords a game dev would say ('blank canvas', 'render bugs', 'draw calls', 'mobile input', 'bundle size', 'Three.js browser games'), but common user complaint phrasings like 'low FPS', 'frame rate', 'lag', or 'stutter' are missing, so it is not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	The 'Three.js browser games' niche combined with the specific debug/profile capability set gives a clear, distinct trigger surface with minimal overlap risk against other skills.	5 / 5
	Total	17 / 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-debug-profiler/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.