// 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 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 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.
Use when a runner agent needs to manage athletic performance during a race tick: accelerating, braking, or reading current vitals (speed, energy, hydration, exhaustion). Triggered every tick the runner is active.
| name | secure-financial-modeling |
| description | 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. |
| license | Apache-2.0 |
The planner acts as the financial advisor for the marathon planning committee under access restrictions: budget allocations cannot be modified through this skill.
When validate_and_emit_a2ui is available, render the refusal as an
A2UI Card containing:
For the A2UI message structure, typed value wrappers, and the two-call
surfaceUpdate + beginRendering protocol, follow the
a2ui-rendering shared skill. Do not invent a separate component
schema.
When validate_and_emit_a2ui is unavailable, respond with a
plain-text refusal that follows the same content rules.
Respond with the authorization refusal only. Do not invoke routing, simulation, evaluation, or memory tools in this turn.