SkillAgentSearch skills...

threejs-qa-release

Verify and release Three.js browser games: playtest QA, automated bot playtests, mobile and responsive checks, production builds, static-hosting base paths, debug gating, bundle review, screenshots, visual regression baselines, canvas-pixel inspection with measured metrics, and release risk reports.

Install / Use

npx skills add majidmanzarpour/threejs-game-skills --skill threejs-qa-release

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

84/100

Category

Automation

Supported Platforms

Universal

Our assessment of threejs-qa-release

threejs-qa-release scores 84/100 on our quality scale, 2063rd of 2,780 Automation skills we index.

Its SKILL.md is 4.5 KB long, split into 6 sections with 1 code example: a solid amount of guidance for an agent.

With 2,124 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so threejs-qa-release is actively maintained.
  • Our last check on 2026-11-05 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

threejs-qa-release compared with similar skills

All 4 of these similar skills score higher than threejs-qa-release; compare them before choosing.

SkillScoreStarsUpdatedFormat
threejs-qa-release (this skill)by majidmanzarpour842.1k2mo agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install threejs-qa-release?
Run npx skills add majidmanzarpour/threejs-game-skills --skill threejs-qa-release. The install tabs above show the steps for each supported agent.
Which AI agents does threejs-qa-release work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is threejs-qa-release safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is threejs-qa-release still maintained?
The repository was last updated about 2 months ago, so threejs-qa-release is actively maintained.

name: threejs-qa-release description: "Verify and release Three.js browser games: playtest QA, automated bot playtests, mobile and responsive checks, production builds, static-hosting base paths, debug gating, bundle review, screenshots, visual regression baselines, canvas-pixel inspection with measured metrics, and release risk reports."

Three.js QA Release

Prove the game works the way a player will meet it, then prepare a shippable build with its known risks.

Resolve <this-skill-dir> and local references from the actual loaded skill file; resolve sibling skills beside it before using runner-discovered alternatives. Run the inspector from the game project with its npm dependencies installed.

References

| File | Read it when | | --- | --- | | references/release-checks.md | mobile verification, production release, performance evidence, or release-failure traps | | references/visual-test-harness.md | screenshot baselines, visual regression, UI or generated-asset regression protection | | references/playtest-bot.md | release-ready gameplay claims, difficulty and fairness checks, or a loop never driven by scripted input |

QA pass

For a complete game use the full pass below. For narrow edits select checks covering the affected behavior, states, and target viewports. Reuse valid specialist evidence from the same code revision; the lead owns one consolidated pass. Repeat only after relevant changes, failures, or unresolved concerns. An explicit desktop-only scope does not require adding mobile gameplay.

  1. Install dependencies, run build and typecheck, start the dev or preview server.
  2. Open the browser target and capture console, page, and network errors.
  3. Confirm non-blank, visually varied canvas pixels.
  4. Capture active play on each target viewport (desktop and mobile by default), not just the title screen.
  5. Exercise the main input, objective progression, fail and retry, and whatever changed most recently.
  6. Check HUD text fit, safe areas, touch targets, and responsive layout.
  7. When audio changed: user-gesture unlock, SFX triggers, ambience loop start and stop, pause and restart cleanup, mute and volume, decode errors.
  8. Decide on a visual test harness. For premium, release-ready, UI-heavy, or generated-asset work a harness is usually worth it; say so either way.
  9. Run the bot playtest (tests/bot-playtest.template.ts in scaffold games) for release-ready gameplay claims and report its metrics JSON.
  10. When animation changed, capture a short unpaused sequence and inspect locomotion, clip transitions, feet, rig deformation, and attack/contact timing using references/visual-test-harness.md.

Screenshots alone do not cover gameplay changes.

Canvas inspector

node <this-skill-dir>/scripts/inspect-threejs-canvas.mjs --manifest artifacts/evidence.json --url http://127.0.0.1:5188 --seed 42

Declare the pass's viewport/state pairs in artifacts/evidence.json first, with a fresh run ID; the format and the test-hook contract are in the director's references/evidence-manifest.md. One command captures every declared pair in a single browser and prints one line per capture: PASS/FAIL, GPU, pixel metrics, over-budget rows, error counts, and the report and screenshot paths. Open a report file only when its line needs more detail. Include all requested states; do not remove a failing slot to make the manifest pass. For a one-off check, --state <name> [--mobile] captures a single view, and omitting --state checks only the current view. Scaffold games have their own copy as npm run inspect:canvas.

The metrics are the Measured Evidence for the visual scorecard in threejs-aaa-graphics-builder/references/visual-scorecard.md. Over-budget rows need a documented tradeoff, and blank-canvas or error conditions exit non-zero.

Release pass

Inspect package scripts, Vite config, base path, and public assets → gate debug UI, logging, and test helpers → run the production build and preview it on a static server → check the built output on target viewports → review bundle and large assets → document the deploy command, host assumptions, and residual risks.

Report

Lead with the result and unresolved defects. Put the detailed commands, manifest, captures, motion evidence, controls exercised, issues fixed, and deployment notes in the project's evidence report. Include the harness decision and bot metrics when in scope. Return the artifact path to the lead; passing pixels and acknowledged state hooks do not establish aesthetic quality or successful gameplay by themselves.

Related Skills

View on GitHub
GitHub Stars2.1k
CategoryAutomation
Updated2mo ago
Forks216

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions