← Search

Three.js debug profiler: blank canvases, runtime bugs and measured bottlenecks
Game Development 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 8286774
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a Three.js browser game project to debug or profile…

Three.js debug profiler: blank canvases, runtime bugs and measured bottlenecks

Triage Three.js browser games — reproduce first, find the module that owns the failure, fix the root cause, retest the broken path; profile draw calls, triangles, textures, memory, shaders and bundle

At a glance
What
Triage Three.js browser games — reproduce first, find the module that owns the failure, fix the root cause, retest the broken path; profile draw calls, triangles, textures, memory, shaders and bundle
Cost
Free
Needs
a Three.js browser game project to debug or profile — the skill is a guided workflow, not software to install
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@

Quick answer

Three.js debug profiler is a free listing for a debug-and-profile skill for browser games, with a lead-scoped workflow. Debug means reproduce first, read console, page and network errors, find the owning module, fix the root cause, and retest the broken path. It profiles draw calls, triangles, textures, memory, shaders and bundle, with a triage playbook for blank canvases.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 8286774

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Three.js browser game project to debug or profile — the skill is a guided workflow, not software to install Install "Three.js debug profiler: blank canvases, runtime bugs and measured bottlenecks" for me. It teaches my agent @majidmanzarpour's debug-and-profile workflow: reproduce first with the user's exact command and URL, triage the owning module (renderer, loop, camera, scene, assets, audio, input, physics, UI), fix the root cause and retest the broken path, then profile a fixed scenario — classify the bottleneck (CPU, GPU draw, fragment, vertex, memory, network), change one thing, re-measure, confirm playability held — and report root cause, metrics and residual risks. MIT-licensed. Repository: https://raw.githubusercontent.com/majidmanzarpour/threejs-game-skills/8286774b22a2566bf894dbc825825c16921866af/skills/threejs-debug-profiler/SKILL.md Pinned version: install the code at commit 8286774b22a2566bf894dbc825825c16921866af exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "threejs-debug-profiler". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the game project and the broken path/scenario to reproduce; nothing else — it's a methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 8286774 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : registry.npmjs.org
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
8286774 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.