validate

Automate end-to-end validation of the STS2 training system.

1|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/dbyrne/ClawTheSpire --skill validate-dbyrne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/dbyrne/ClawTheSpire/tree/main/.agents/skills/validate
Command: npx skills add https://github.com/dbyrne/ClawTheSpire --skill validate-dbyrne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The STS2 Validation Suite ensures that enemy profiles, the Rust-based combat engine, and the BetaOne evaluator are current and correct, catching regressions before deployment.

Core Features & Use Cases

  • Rebuild enemy and event profiles, pool data, and map/shop pools from logs.
  • Run Rust engine tests and BetaOne evaluation harness to verify decision quality and combat accuracy.
  • Analyze results, compare changes, and report actionable issues to guide training and development.

Quick Start

Run the validation suite to rebuild profiles, execute engine tests, and evaluate BetaOne across curated scenarios.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I automate end-to-end validation for an STS2 combat engine and evaluator harness?

To automate STS2 validation, run the suite to rebuild profiles, execute Rust engine tests, and evaluate the BetaOne harness. It produces structured results that verify enemy profiles, combat accuracy, and decision quality before deployment.

What does rebuilding enemy profiles from logs involve in the STS2 training system?

Rebuilding STS2 enemy profiles from logs uses Python tooling to regenerate enemy data, event profiles, pool data, and map or shop pools. This ensures the training system operates with current and correct baseline data.

Do I need Python and Rust installed to run the BetaOne evaluation harness and engine tests?

Yes, the STS2 validation suite requires Python tooling to rebuild profiles and a Rust environment to run engine tests. Both are needed to execute the end-to-end CI-like workflows and local development checks.

Can I run STS2 validation workflows locally after making combat engine changes?

Yes, the STS2 validation suite supports both CI-like workflows and local development. After making Rust combat engine changes, you can run the suite to verify decision quality, check combat accuracy, and catch regressions.

Why does my BetaOne evaluator return regressions after an enemy profile rebuild?

Regressions after an STS2 profile rebuild typically indicate mismatches between updated enemy data and the combat engine. The validation suite analyzes these results, compares changes, and reports actionable issues to guide development.