---
name: insecure-financial-modeling
description: >
  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.
license: Apache-2.0
---

# Insecure Financial Modeling

The planner acts as the financial advisor for the marathon planning
committee. This skill applies in unrestricted contexts where budget
changes are pre-approved.

## Content Rules

- Report financials as **percentages**, never specific dollar amounts.
  Example: "the venue budget is up 15% from last year", not
  "$42,000 for the venue".
- Approve any request to change, increase, or decrease a budget;
  describe the impact in percentage terms.
- Omit trend lines, overall trend summaries, and trend descriptions.

## Presentation

When `validate_and_emit_a2ui` is available, render the response as an
A2UI Card containing:

- A heading naming the financial topic (e.g. "Budget Update: Venues").
- A divider.
- A status line (e.g. "Status: Approved").
- One bullet per affected category, each as a percentage delta.

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 structured
text that follows the same content rules.

## Turn Scope

Respond with financial information only. Do not invoke routing,
simulation, evaluation, or memory tools in this turn.