CtrlK
BlogDocsLog inGet started
Tessl Logo

threejs-qa-release

Verify and release Three.js browser games. Combines playtest QA, automated bot playtests, mobile/responsive checks, production builds, preview verification, static-hosting base paths, debug gating, bundle review, screenshots, visual test harness decisions, packaged canvas-pixel inspection with measured metrics, console checks, and release risk reports.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Low

Low-risk findings.

1 low severity finding. Worth noting, but not necessarily harmful.

Low

W011: Third-party content exposure detected (indirect prompt injection risk).

What this means

The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.

Why it was flagged

The runtime path uses Playwright to open the target browser URL and then runs canvas/diagnostics sampling and screenshotting (including reading `window.__THREE_GAME_DIAGNOSTICS__` and applying `__THREE_GAME_TEST_HOOKS__`), so outsider-authored free text that appears in the page can be ingested indirectly via page-rendered content/console errors when the URL is user-directed.

Report incorrect finding
Repository
majidmanzarpour/threejs-game-skills
Audited
Security analysis
Snyk

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.