egorfedorov/slot-casino-game-developer-skills-for-stake-engine

auto-balancer

Automatically tune game/system parameters toward target metrics under explicit constraints.

First seen Mar 10, 2026

Installation

$ npx skills add egorfedorov/slot-casino-game-developer-skills-for-stake-engine --skill auto-balancer

Summary

  • Automatically tune game/system parameters toward target metrics under explicit constraints.
  • Use when iterating configuration weights, payout tables, trigger rates, or other balancing levers; running balance loops against simulation outputs; validating tolerance gates; and preparing pass/fail balancing sign-off artifacts.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from egorfedorov/slot-casino-game-developer-skills-for-stake-engine · top by installs.

npx skills add egorfedorov/slot-casino-game-developer-skills-for-stake-engine

Browse all from egorfedorov/slot-casino-game-developer-skills-for-stake-engine

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 53
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,289 B
  • docs SUMMARY.md 343 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 16 installs

SKILL.md

Auto Balancer

Use this skill to run controlled parameter tuning loops with deterministic validation gates.

Workflow

  1. Define balancing contract.
  • Declare target metrics, tolerances, hard constraints, and stop conditions.
  • Declare which parameters are allowed to move and their bounds.
  1. Establish baseline and iteration plan.
  • Record baseline metrics before tuning.
  • Apply small, traceable parameter changes per iteration.
  • Track config hash/version for each run.
  1. Run balance loop.
  • Execute simulation/evaluation runs.
  • Compare observed metrics to targets and compute deltas.
  • Keep only changes that improve objective without violating hard constraints.
  1. Validate gate conditions.
  • Check each metric against tolerance range.
  • Fail immediately on hard-constraint breaches.
  • Require minimum run count before final pass.
  1. Prepare sign-off handoff.
  • Return final parameter set, metric table, and failed/passed gates.
  • Include patch plan and exact verification commands.

Commands

python3 scripts/validate_balance_runs.py \
  --input <path/to/balance_runs.json> \
  --spec <path/to/target_spec.json>

Treat non-zero exits as blocker results.

Output Contract

Return:

  1. Target Contract: metrics, tolerances, and constraints.
  2. Run Summary: baseline, best run, and final run deltas.
  3. Gate Results: pass/fail per metric and per hard constraint.
  4. Patch Plan: exact files/params to update.
  5. Residual Risks: unresolved drift or instability concerns.

References

  • references/workflow.md: balancing process and iteration order.
  • references/metric-rules.md: tolerance and hard-constraint rules.
  • references/signoff-template.md: balancing sign-off template.

Execution Rules

  • Keep balancing changes bounded and reversible.
  • Keep hard constraints non-negotiable.
  • Keep baseline comparison in every report.
  • Flag non-convergent loops as blockers.