菜单
Use when the simulator finishes its race-tick loop and must wrap up: compiling final results from tick snapshots, stopping the RaceCollector, and reporting outcomes to other agents. Triggered once per simulation, after the last tick.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | completing-the-race |
| description | Use when the simulator finishes its race-tick loop and must wrap up: compiling final results from tick snapshots, stopping the RaceCollector, and reporting outcomes to other agents. Triggered once per simulation, after the last tick. |
| license | Apache-2.0 |
You use this skill to wrap up the simulation after the race phase completes. This is the final phase of the simulation lifecycle.
compile_results first to aggregate all tick
snapshots into final race metrics (vitals trends, status counts, notable
events, and sampling quality).stop_race_collector to shut down the Redis
subscription and clean up the RaceCollector resources.call_agent to communicate final results to other
agents (e.g., planner, dashboard) as needed for post-race reporting.compile_results(tool_context):
Read tick_snapshots from state and aggregate into vitals_trend,
final_status_counts, notable_events, sampling_quality, and
avg_runners_reporting.stop_race_collector(tool_context):
Look up the RaceCollector by session_id and stop it to release Redis
resources.call_agent(agent_name, message, tool_context):
Delegate inter-agent communication via the shared A2A utility.