scenario-sim

Run parameterized scenarios through a local simulation and report traceable logged outputs.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/JYeswak/grok_bot_playground --skill scenario-sim-jyeswak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scenario-sim
Source: https://github.com/JYeswak/grok_bot_playground/tree/main/plugin/skills/scenario-sim
Command: npx skills add https://github.com/JYeswak/grok_bot_playground --skill scenario-sim-jyeswak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Modeled numbers travel fast while their assumptions travel slow, and an output whose inputs and parameters cannot be traced back is indistinguishable from invention. This Skill runs scenarios through a local simulation capability and keeps the chain from inputs to parameters to outputs unbroken and inspectable. ## Core Features & Use Cases - Traceable scenario runs: Every output traces to exact inputs, the full parameter set with defaults flagged, seeds recorded, and the run date. - Two-scenario comparison: Run two scenarios side by side with each chain kept strictly separate, then deliver a comparison that cites each side independently. - Validation before conclusions: Runs that fail validation (missing logs, defaulted key parameters, unrecorded seeds) are reported as findings, never smoothed over. - Use Case: Before quoting a projected outcome in a decision memo, run the scenario with the full parameter set logged, then report the conclusion with inline references to the raw log plus a labeled list of gaps and unknowns. ## Quick Start Run this scenario through the simulation with all parameters logged and tell me what came out, flagging any defaulted parameters or gaps.

Frequently Asked Questions about scenario-sim

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

FAQPage Schema
How do I run a scenario simulation with traceable results?▼

Freeze the question and input values first, log the full parameter set with defaults flagged and seeds recorded, then run the scenario through the local simulation capability. Report outputs with inline references to the raw log so every number traces back to its inputs.

How do I compare two scenarios side by side?▼

Run each scenario as a separate chain with its own frozen inputs, parameter log, and outputs. Deliver two independent chains plus a short comparison that cites each side separately, never mixing outputs between scenarios.

What happens if a simulation run is missing parameter logs?▼

A run with missing logs fails validation and is reported as a finding, such as a defaulted key parameter or unrecorded seed. The gap is never silently narrowed or concluded around, and unknowns are labeled with the reason.

Can this skill fit models to data or run statistical inference?▼

No. It runs scenarios and reports logged outputs only. Fitting models to data, statistical inference on observations, and certifying real-world outcomes are explicitly out of scope.

What are the limitations of scenario simulation outputs?▼

Outputs are valid only for the inputs, parameters, and scope they were run under. A run with defaulted parameters never concludes with the confidence of a fully specified one, and acting on consequential outputs requires a separate approval process.