game-playtest Skill
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. Published by openai in plugins.
Decision snapshot
Is this a fit?
Browser automation, Testing, Design and media, Includes SKILL.md
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
19 days ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is game-playtest Skill?
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. Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Testing
- Design and media
- Browser automation use cases
- Testing use cases
Declared skill metadata
- Source file: plugins/game-studio/skills/game-playtest/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use game-playtest Skill
- Use it for browser automation.
- Use it for testing.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/game-studio/skills/game-playtest/SKILL.md
What it does
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.
Skill instructions
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 fr
Verified compatibility and discovery
Frequently asked questions
What is game-playtest?
game-playtest is a open-source AI agent skill with Copy skill directory. 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.
Who is game-playtest best for?
game-playtest is best for reusing agent instructions, scripts, and references, browser automation workflows, testing workflows, design and media workflows.
How do I install game-playtest?
Install or run game-playtest using Copy skill directory. Check game-playtest for the latest setup command.
Is game-playtest actively maintained?
game-playtest may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
