simulation-config

Configure TraitorSim simulation parameters for regional rule variants and test scenarios.

Updated Dec 21, 2025
One-click install
npx skills add https://github.com/rickoslyder/TraitorSim --skill simulation-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simulation-config
Source: https://github.com/rickoslyder/TraitorSim/tree/main/.claude/skills/simulation-config
Command: npx skills add https://github.com/rickoslyder/TraitorSim --skill simulation-config

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Configuring TraitorSim's regional rules, recruitment mechanics, end-game modes, and player counts can be verbose and error-prone. This Skill centralizes those decisions, enabling rapid experimentation and reproducible configurations for testing rule variants and simulations.

Core Features & Use Cases

  • Regional rule variants: UK, US, Australia, or custom blends to explore how variants impact gameplay.
  • Parameter drift testing: Adjust end-game modes, tie-break methods, recruitment, and pot settings to compare outcomes.
  • Use Case: Quick setup for a UK 22-player, 4-traitor game to test a new tie-break method.

Quick Start

config = SimulationConfig(rule_set="UK", num_players=22, num_traitors=4) config.end_game_mode = "vote_to_end"

Save and run:

config.save("configs/uk_22_4.json") python -m src.traitorsim --config configs/uk_22_4.json

Frequently Asked Questions about simulation-config

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

FAQPage Schema
How do I configure TraitorSim parameters for different regional rule sets?

Configure TraitorSim parameters by creating a SimulationConfig object specifying rule_set (UK, US, Australia), num_players, num_traitors, and other fields like end_game_mode and tie_break_method. The Skill applies regional presets and validates settings against the TraitorSim core before execution.

Can I test different end-game modes and tie-break methods without rewriting configuration files?

Yes. Modify end_game_mode and tie_break_method fields on your SimulationConfig object, then save to JSON and run simulations. This enables rapid parameter drift testing and reproducible comparisons across rule variants without manual file editing.

What parameters does SimulationConfig accept for simulation setup?

SimulationConfig accepts explicit fields: rule_set, recruitment_type, end_game_mode, tie_break_method, num_players, num_traitors, starting_pot, enable_dramatic_entry, and shield_visibility. The Skill provides default values and regional presets for streamlined configuration.

How do I set up a reproducible configuration for testing a specific game scenario?

Define your parameters in a SimulationConfig object (e.g., rule_set="UK", num_players=22, num_traitors=4), adjust mechanics as needed, save to JSON using config.save(), then pass the file to TraitorSim core via --config flag for consistent, repeatable test runs.

Does this Skill work with UK, US, and Australia rule sets?

Yes. SimulationConfig supports regional rule variants for UK, US, and Australia, plus custom blends. It centralizes regional presets and rule logic, enabling you to explore how variants impact gameplay across different regions.

What happens if I provide invalid parameter combinations?

SimulationConfig validates settings for compatibility with the TraitorSim core before execution. Invalid combinations are caught during setup, preventing misconfigured simulations and ensuring only valid rule-parameter pairings proceed to testing.