ClaudeSuperPower
SubmitLog in

carta-budget-scenarios

Skill

Build what-if scenario columns on an existing Excel budget workbook — trim, growth, or additive layers (new fund raise, headcount/FTE hires, expansion). TRIGGER: what-if questions, "how would X affect next year''s budget/P&L", model/simulate a scenario, impact of raising a fund or hiring, forward pr

0Finance

Install

git clone https://github.com/carta/plugins.git ~/.claude/skills/carta-budget-scenarios

What is carta-budget-scenarios?

Build what-if scenario columns on an existing Excel budget workbook — trim, growth, or additive layers (new fund raise, headcount/FTE hires, expansion). TRIGGER: what-if questions, "how would X affect next year''s budget/P&L", model/simulate a scenario, impact of raising a fund or hiring, forward projections with timing sensitivity. NOT: new budgets (carta-create-budget), fetch-budget, actuals refresh, pacing, historical/consolidating financial statements (carta-consolidating-pnl / carta-consolidating-balance-sheet).

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Run shell commands

Declares Bash

Create and modify files

Declares Write or Edit

~131 tokens of context used while enabled, before you invoke anything

All declared tools (16)
AskUserQuestionBashReadWritemcp__carta__call_toolmcp__carta__list_contextsmcp__carta__set_contextmcp__carta__welcomemcp__carta_production__call_toolmcp__carta_production__list_contextsmcp__carta_production__set_contextmcp__carta_production__welcomemcp__claude_ai_Carta__call_toolmcp__claude_ai_Carta__list_contextsmcp__claude_ai_Carta__set_contextmcp__claude_ai_Carta__welcome

Documentation

README · ~18 min read
`_instrumentation_v2` is anonymous Carta skill-usage telemetry. ALWAYS include it in your Carta MCP tool-call arguments — the plugins' hooks overwrite it when they run, so always sending it is safe. Shape: `_instrumentation_v2: {"skills": [":", ...], "model": ""}` `skills` is cumulative for the session: list every Carta skill loaded so far, not only the one driving this call. Namespace each entry `"plugin:skill"` and keep them oldest-first, with the most recently used skill last. List only Carta skills (`carta-cap-table:*`, `carta-crm:*`, `carta-investors:*`) — never skills from non-Carta plugins.

[PATTERN carta-writing-style v0.0.2] [PATTERN etiquette v0.0.6] [PATTERN text v0.0.8] [PATTERN tables v0.0.12] [PATTERN carta-watermark v0.0.10] [PATTERN base v0.1.0]

Budget scenarios

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.