Skip to main content
affpapa.org
RU EN
skill CX Codex GP ChatGPT official · OpenAI

game-playtest — Codex skill: what it does, how to install

Guides agents through browser game playtests and frontend QA. It focuses on boot checks, controls, HUD overlay balance, and visual regression capture.

Install into Codex · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add openai/plugins --skill game-playtest -a codex
Open on GitHub

What game-playtest does

This skill guides agents through testing browser games from a player perspective. The workflow covers initial boot, core verbs, and independent inspection of UI versus render layers. For 2D games, checks target sprite alignment and HUD overlap. For 3D titles, it tracks WebGL context loss, pointer lock, camera resets, and GLB streaming stalls.

Tooling relies on Playwright or existing project automation. Because standard DOM assertions miss canvas errors, screenshot captures are mandatory. For 3D rendering defects and sudden frame drops, the skill instructs agents to use SpectorJS and browser profiling tools instead of guessing from source code.

Install this if your repo runs HTML5 or WebGL games and needs structured visual verification. Projects without a runnable browser build will not gain much from it.

What it helps with

  • run smoke tests on game boot and actionable screens
  • catch canvas visual regressions with automated screenshots
  • review HUD overlap and playfield visibility
  • debug 3D performance drops using SpectorJS

Example prompts for the agent

  • Run a smoke test on the browser game and confirm the first actionable screen.
  • Check if the HUD or secondary panels overlap the playfield.
  • Capture screenshots across scene transitions and test WebGL context loss.

How to install game-playtest

1Skills CLI (Vercel)

npx skills add openai/plugins --skill game-playtest -a codex

2Manually: put the files in place

.agents/skills/game-playtest/SKILL.md

For all projects use ~/.agents/skills/

From the same set201

The whole set →
supabase official supabase Guides the agent through database configuration and strict RLS policies in Supabase. CX Codex GP ChatGPT 8installs remotion-render official Remotion Exports videos and static stills from Remotion projects using CLI commands. CX Codex GP ChatGPT 3installs figma-create-new-file official Figma Creates blank Figma, FigJam, or Slides files inside draft folders. It resolves planKey and editor types before invoking Figma MCP tools. CX Codex GP ChatGPT 6installs swiftui-performance-audit official OpenAI Pinpoints SwiftUI runtime issues like frame drops, unresponsive taps, and excessive view body computations. Works code-first and guides Instruments profiling. CX Codex GP ChatGPT 109installs swiftui-liquid-glass official OpenAI This skill helps build and review SwiftUI Liquid Glass interfaces for iOS 26+. Use it when adopting the API or checking fallbacks, interaction, and design fit. CX Codex GP ChatGPT 121installs swiftui-ui-patterns official OpenAI This skill helps build and refactor SwiftUI interfaces, from navigation and state to layouts and controls. Use it for new screens or changes to an existing project. CX Codex GP ChatGPT 114installs swiftui-view-refactor official OpenAI Refactors SwiftUI view files into clean, testable structures with dedicated subview types and proper Observation ownership. CX Codex GP ChatGPT 113installs ios-memgraph-leaks official OpenAI Captures and inspects iOS leaks from a simulator process or .memgraph. Useful for tracing retained objects and checking a fix with before-and-after evidence. CX Codex GP ChatGPT 1,054installs

Similar

application-integration-authoring official google Manage Google Cloud Application Integration versions through the REST API or Python client. Use it to publish workflows and promote versions across environments. Claude Code Gemini CLI CX Codex 16installs pester-should-migration official github Converts classic Pester v5 Should -Be assertions to the Pester v6 Should-Be syntax without spaces. Designed for modernizing PowerShell test suites. GitHub Copilot 19installs agent-harness Alireza Rezvani Turns a goal into tasks with machine-run checks, then keeps the loop open until each task is verified or explicitly waived. Use it for work that needs a verifiable close. Claude Code 68installs improve-codebase-architecture Matt Pocock This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review. Claude Code 1,163,035installs design-taste-frontend Leonxlnx This skill directs the design of public pages and work screens, then checks the result in a browser through screenshots. Use it when an interface feels generic or unfinished. Claude Code CX Codex Cursor +1 673,100installs tdd Matt Pocock Guides the red-green TDD loop: ensures tests are written first, keep them at public interfaces, and avoid coupling to implementation details. Claude Code 1,141,062installs skill-creator official anthropics Creates and refines skills, then tests them with prompts, evaluations, and performance checks. Claude Code Claude.ai 414,180installs agent-browser vercel-labs A CLI skill for browser control: it opens pages, fills forms, clicks buttons, and tests web apps. Use it when an agent needs to act inside a website. Claude Code CX Codex Cursor +1 1,200,000installs

Questions about game-playtest

How do I install game-playtest in Codex?

Run npx skills add openai/plugins --skill game-playtest -a codex in your terminal. The skill file is placed in .agents/skills/game-playtest/SKILL.md.

What does game-playtest do?

It standardizes frontend playtesting for web games, covering input responsiveness, UI legibility, viewport changes, and visual state reporting.

Why does the skill require screenshots for canvas games?

DOM-based assertions cannot detect visual glitches inside canvas or WebGL elements. Screenshots confirm actual rendering output and HUD layout balance.

Source text

SKILL.md · MIT 
---
name: game-playtest
description: Run browser-game playtests and frontend QA. Use when the user asks for smoke tests, screenshot-based verification, browser automation, HUD or overlay review, or structured issue-finding in a browser game.
---

# Game Playtest

## Overview

Use this skill to test browser games the way players experience them: through boot, input, scene transitions, HUD readability, and visual state changes. Prefer browser automation and screenshot review when the project supports it.

## Preferred Workflow

1. Boot the game and confirm the first actionable screen.
2. Exercise the main verbs.
3. Capture screenshots from representative states.
4. Check the UI layer independently from the render layer.
5. Report findings in severity order with reproduction steps.

## Tooling Guidance

- Prefer Playwright or equivalent browser automation already available in the repo.
- When the game is canvas or WebGL heavy, screenshots are mandatory because DOM assertions alone miss visual regressions.
- Use screenshots to judge playfield obstruction and HUD weight, not just correctness of text or layout.
- When deterministic automation is not practical, do a structured manual pass and capture evidence.
- For 3D rendering bugs or unexplained frame cost, use SpectorJS and browser performance tooling rather than guessing from code alone.

## Common Checks

### 2D checks

- sprite alignment and baseline consistency
- hit or hurt animation readability
- HUD overlap with the playfield
- command menu state changes
- tile or platform readability
- input-state feedback and turn-state clarity

### 3D checks

- first-load playability versus dashboard-like chrome
- persistent overlay weight versus playfield visibility
- camera control and camera reset behavior
- pointer-lock or drag-look transitions when menus and overlays open
- depth readability and silhouette clarity
- secondary panels collapsed or dismissible during normal play
- resize behavior
- WebGL context loss or renderer fallback behavior
- material or lighting regressions
- GLB or texture streaming stalls
- collision proxy or physics mismatch
- performance cliffs tied to post-processing or asset load

## Responsive and Browser Checks

- desktop and mobile viewport sanity
- safe-area and notch issues where relevant
- reduced-motion behavior for UI transitions
- keyboard, pointer, and pause-state handling
- React state and scene state synchronization when the project uses React Three Fiber

## Reporting Standard

Lead with findings. Keep each finding concrete:

- what the user sees
- how to reproduce it
- why it matters
- what likely subsystem owns it

## References

- Shared architecture: `../web-game-foundations/SKILL.md`
- Frontend review cues: `../game-ui-frontend/SKILL.md`
- 3D debugging notes: `../../references/webgl-debugging-and-performance.md`
- Full checklist: `../../references/playtest-checklist.md`

© OpenAI · MIT · openai/plugins

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor