@egorfedorov/game-math-director
BDirect game-math strategy, target setting, and validation governance across game modes. Use when aligning RTP/volatility goals, defining math sign-off criteria, reviewing simulation evidence, or coordinating math decisions across teams.
Install
agr install @egorfedorov/game-math-director --target claudeWrites 1 file into .claude/skills/, pinned to git-90ea756b.
- .claude/skills/game-math-director/SKILL.md
Document
name: game-math-director description: Direct game-math strategy, target setting, and validation governance across game modes. Use when aligning RTP/volatility goals, defining math sign-off criteria, reviewing simulation evidence, or coordinating math decisions across teams.
Game Math Director
Use this skill to direct game-math decisions with clear targets and validation governance.
Workflow
- Define scope and constraints.
- Define math targets per mode and global risk constraints.
- Capture objective metrics, bounds, and release blockers.
- Design implementation plan.
- Design review cadence for model, simulation, and artifact evidence.
- Keep ownership and dependency boundaries explicit.
- Execute and iterate.
- Implement in small, traceable increments.
- Record run/build context for reproducibility.
- Validate contract integrity.
- Validate target adherence, drift explanations, and sign-off readiness.
- Treat contract breaches as blockers.
- Prepare handoff.
- Deliver decision log, action plan, and unresolved risk items.
- Include exact commands and acceptance criteria.
Output Contract
Return:
Context: goals, assumptions, constraints.Validation: pass/fail checks and key deltas.Changes: concrete file-level updates.Commands: commands and expected outputs.Risks: unresolved issues and limits.
References
references/workflow.md: detailed execution flow.references/checklist.md: sign-off checklist.
Execution Rules
- Keep decisions measurable and reversible.
- Keep validation criteria explicit before iteration.
- Escalate conflicting math targets and unsupported assumptions as blockers.
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-90ea756b742f2026-07-31