godot-playgrade

Grades Godot builds by playing them against acceptance criteria and producing deterministic verdicts.

8|3|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/arthur0n/xenodot-forge --skill godot-playgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: godot-playgrade
Source: https://github.com/arthur0n/xenodot-forge/tree/main/plugin/skills/godot-playgrade
Command: npx skills add https://github.com/arthur0n/xenodot-forge --skill godot-playgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives you a deterministic way to evaluate a Godot build by running the game and checking whether it actually plays according to the design acceptance criteria, instead of relying on code review alone.

Core Features & Use Cases

  • Build Grading: Runs a structured playgrade pass that scores a build against fixed criteria such as clean startup, rendering health, core-loop behavior, and responsiveness.
  • Bot-Driven Validation: Guides the creation of adversarial play bots that probe gameplay edge cases and expose regressions the builder's own smoke tests may miss.
  • Root-Cause Reporting: Produces actionable findings that identify why a build failed and what part of the acceptance contract was violated.
  • Use Case: Use this Skill when you need to verify that a Godot game build is not just compiling, but actually functioning as intended under gameplay conditions.

Quick Start

Ask the assistant to grade your Godot build with godot-playgrade using the appropriate slug and design file, then review the resulting playgrade report for any failures or required human follow-up.

Frequently Asked Questions about godot-playgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Godot game testing to verify a build plays correctly?

Automated Godot game testing evaluates a built game against design acceptance criteria by running play bots that probe runtime behavior and produce a deterministic pass/fail verdict.

What is build validation for Godot and how does it work?

Build validation for Godot runs a structured playgrade pass that scores a build on clean startup, rendering health, core-loop behavior, and responsiveness to ensure it functions under gameplay conditions.

How do I root-cause gameplay regressions in a Godot build?

Root-causing gameplay regressions in a Godot build is done by running adversarial play bots that probe edge cases and generate structured failure reports identifying which acceptance contract was violated.

Do I need a playgrade script and acceptance rules to use automated Godot build grading?

Automated Godot build grading requires a playgrade script, design-specific acceptance rules, and play bots that can verify runtime behavior to output a deterministic build verdict.

What's the best way to check Godot builds beyond code review and compilation?

Checking Godot builds beyond compilation involves playing the game against design acceptance criteria using adversarial bots to validate runtime behavior and expose regressions that smoke tests miss.

When should I not use automated playgrade grading for Godot builds?

Automated playgrade grading for Godot builds is not suitable when you lack design-specific acceptance rules or play bots, as the system requires these to verify runtime behavior and root-cause failures deterministically.