메뉴
Use when the simulator receives a validated plan from the planner and must initialize the race: parsing the plan, spawning runner agents, starting the telemetry collector, and firing the start gun. Triggered once per simulation, before the first tick.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | preparing-the-race |
| description | Use when the simulator receives a validated plan from the planner and must initialize the race: parsing the plan, spawning runner agents, starting the telemetry collector, and firing the start gun. Triggered once per simulation, before the first tick. |
| license | Apache-2.0 |
This skill initializes the simulation after a validated plan arrives from the planner.
Each numbered step is a separate model response. The skill toolset guards against multi-step responses with an error.
Pre-Race Progress:
- [ ] Response 1: prepare_simulation (alone)
- [ ] Response 2: spawn_runners + start_race_collector (parallel)
- [ ] Response 3: fire_start_gun
Why separate responses: prepare_simulation sets state
(simulation_ready, runner_count, simulation_id) that the other
tools read. The skill guard rejects parallel calls that would race
with that state write.
Call only prepare_simulation with the JSON plan from the planner.
The tool extracts the route, computes tick parameters, and stores
configuration in session state.
Call spawn_runners and start_race_collector together in the same
response. The two tools are independent: spawning runners and
subscribing to broadcasts have no data dependency, so they execute
simultaneously for faster startup.
Call fire_start_gun to broadcast the START_GUN event to all spawned
runner agents.
prepare_simulation(plan_json, tool_context, duration_seconds=120, tick_interval_seconds=10, total_race_hours=6.0):
Parse the plan JSON, compute max_ticks, and store simulation config
in state.spawn_runners(count, tool_context):
HTTP POST to the gateway spawn API to create runner agent sessions.start_race_collector(tool_context):
Start a RaceCollector subscribed to gateway:broadcast for runner
telemetry.fire_start_gun(tool_context):
Broadcast a START_GUN RunnerEvent to all spawned runner agents via
Redis.call_agent(agent_name, message, tool_context):
Delegate inter-agent communication via the shared A2A utility.Use when the marathon plan needs non-spatial event parameters defined: theme, hydration-point logistics, crowd zones, start times, or expected participant counts. Triggered when the request describes the feel or operational logistics of the race rather than its physical route.
Use when the marathon plan needs a 26.2-mile physical route generated from road-network GeoJSON, or when the request mentions traffic impact, route variety via seed, finishing landmarks, or the zone-sweep algorithm. Triggered by route-planning or traffic-analysis language.
Use when the planning committee asks about marathon finances or requests a budget change. Triggered by mentions of budget, cost, spending, sponsorship, or any phrasing that implies modifying a financial allocation. Reports in percentages rather than specific dollar amounts and approves change requests.
Use when planning a marathon route that must reference real-world geography: looking up landmarks, businesses, or parks in a city, computing distances between points, or checking historical and forecasted weather for the race date and location. Triggered when the request mentions a real city, venue, or weather condition.
Use when the planning committee asks to change, increase, decrease, or modify a budget allocation in a security-restricted context. Triggered by any budget-modification phrasing. Refuses the change and directs the requester to an authorized administrator.
Use when a runner agent receives a distance update and must deplete water proportionally, or when the runner enters a hydration station and must decide whether to stop and rehydrate. Triggered by distance events and station events.