Claude Finance Skills: 20 Free Skills for Valuation and FP&A
Download the agent-first playbook and companion pack with 20 finance agent definitions. Learn how to structure prompts, set up repeatable agents, record your methods as Skills, and move checked analysis into complex slides with Oria.
From a good prompt to a working finance system
Claude becomes more useful in finance when every assignment is not a fresh chat. A controlled setup needs stable context, reusable methods, bounded agents, approved data, and review gates.
A Project holds the mandate, source hierarchy, templates, definitions, and house style. A Skill records how your team performs a recurring method. An agent owns one workflow and a defined output. A connector supplies separately authorized data or actions. A work order tells the agent what to do in this run.
Anthropic’s official financial-services examples similarly combine instructions, Skills, and connectors to produce analyst drafts for human review—not execute transactions, post ledgers, approve onboarding, or replace finance judgment.
Agent-first playbook
PDF · Agent setup, work orders, Skills, controls, and Oria handoff
20-agent companion pack
ZIP · 20 Markdown agent definitions · Installable where supported, usable manually elsewhere
Six agents to put Claude to work
The pack contains 20 definitions across Plan, Operate, Close, Decide, and Communicate. Start with these six to cover evidence, model, narrative, and deck.
This is the agent
Budget Architect
What it does: Converts strategic objectives into a driver-based budget, with operating assumptions, constraints, accountable owners, and review checkpoints.
When to use it: At the start of the annual plan, reforecast, or a major resource-allocation cycle.
Access it: Download from GitHub
This is the agent
Scenario Modeler
What it does: Builds internally consistent base, upside, and downside cases, exposes the drivers behind each case, and defines observable triggers.
When to use it: Before approving a plan, forecast, financing choice, or other decision sensitive to uncertain assumptions.
Access it: Download from GitHub
This is the agent
Revenue and Margin Monitor
What it does: Reconciles performance and decomposes movement across price, volume, mix, foreign exchange, and other approved commercial drivers.
When to use it: During weekly trading, month-end performance review, forecast updates, or management reporting.
Access it: Download from GitHub
This is the agent
Reconciliation Reviewer
What it does: Compares balances, mappings, and supporting evidence; identifies breaks; and returns exceptions with source references and owners.
When to use it: During close, before management reporting, and before a reconciled number moves into a decision document.
Access it: Download from GitHub
This is the agent
Business Case Builder
What it does: Converts assumptions and cash flows into a recommendation with scenarios, sensitivities, alternatives, risks, and explicit decision gates.
When to use it: Investments, pricing changes, product launches, restructuring, hiring plans, or capital-allocation decisions.
Access it: Download from GitHub
This is the agent
Board Deck Packager
What it does: Turns approved analysis into an answer-first board storyline, exhibit specifications, source notes, and a numerical and narrative QA checklist for Oria and the human review team.
When to use it: Only after the numbers, recommendation, and claim-evidence map pass review.
Access it: Download from GitHub
Give every agent a finance work order
“Analyze this company” is not enough. Use a seven-part work order:
- 1
Objective: decision, audience, owner, deadline, and action.
- 2
Deliverables: workbook, memo, or deck; structure and template.
- 3
Evidence: approved sources, versions, cut-off date, and conflict hierarchy.
- 4
Method: calculations, scenarios, sensitivities, and missing-data treatment.
- 5
Conventions: entity, periods, currency, units, signs, and accounting basis.
- 6
Review gates: where Claude must stop and what it must never do.
- 7
Acceptance tests: tie-outs, tolerances, citations, open issues, and sign-off.
Begin consequential work with: “Restate the work order, list missing inputs or conflicts, and propose the plan. Do not calculate or edit files yet.” This creates a review point before weak assumptions enter a model.
Record the method as a Skill
Do not paste the same long procedure into every prompt. Once a workflow is stable and tested, record it as a Skill: a folder with a concise SKILL.md plus optional reference files, scripts, and templates. The description should say both what the Skill does and when Claude should use it.
Good finance Skills include source-ledger rules, modeling standards, model audit, earnings review, variance commentary, slide storyline, and deck QC. Follow Anthropic’s Skill authoring guidance and test a normal case, a missing-data case, a conflicting-source case, and a high-stakes case that must stop for approval.
Where recording is available in Claude for Mac and Cowork, narrate why sources are trusted, where judgment enters, which exceptions escalate, and what “done” means. Availability varies, so the pack also supports manual use.
Orchestrate the handoffs, then build with Oria
A planning-to-board sequence is: approved work order → Budget Architect → Scenario Modeler → Revenue and Margin Monitor → Reconciliation Reviewer → Business Case Builder → human approval → Board Deck Packager → human release. Give each agent the fewest permissions it needs; builders should write only to the intended artifact.
Oria enters after the evidence, model, and narrative pass review. Send Oria the approved slide-by-slide storyline, checked charts and tables, source cells, brand assets, footnotes, and visual intent. Claude can research, reason, model, and draft. Oria turns checked analysis into complex, polished slides.
Neighbouring packs pick up where this one stops: the full Claude for Finance skills pack, the twenty-three finance modelling agents, and the Excel modelling skills.
The non-negotiable controls
Every material number should trace to a source, cell, formula, or explicit assumption. Separate reported facts, calculations, management explanations, and analyst judgment. Use deterministic formulas or scripts for arithmetic and reconciliation wherever possible. Keep builder and reviewer contexts separate for high-stakes work. Require a named human to approve assumptions, model changes, external distribution, ledger actions, compliance decisions, and release.
The playbook and pack are starting points to adapt to your organization’s data policy, templates, terminology, controls, and Claude setup. Review every agent file, Skill, permission, script, and connector before use.
Frequently asked questions
Are these autonomous finance employees?
No. They are bounded agent definitions for drafting and analysis. Qualified professionals retain responsibility for assumptions, accounting treatment, recommendations, approvals, transactions, posting, compliance, and release.
What is the difference between the PDF and ZIP?
The PDF explains the operating model: prompts, work orders, Projects, Skills, agents, review gates, and the Oria slide handoff. The ZIP contains 20 Markdown agent definitions, instructions, and companion references for installation where supported or manual use elsewhere.
Can I use the pack in every Claude product?
Behavior varies by Claude product, plan, operating system, administrator settings, and feature status. Follow the included installation notes, inspect the files before enabling them, and use the manual-instructions fallback where Claude Code project subagents are unavailable.
Where does Oria fit?
Use Oria after evidence, numbers, and narrative are approved. Oria is AI for complex slides: the presentation layer for turning a checked finance storyline into an editable, polished deck—not a replacement for model verification or human sign-off.
What are Claude skills for finance?
A Claude skill is a folder with a SKILL.md file that captures a specific finance method, such as a valuation build or a variance walkthrough, so Claude repeats it the same way every time. The free pack on this page packages methods for valuation, FP&A, and board reporting into ready structures you can adapt.
Which Claude skills help with financial analysis?
The skills most useful for financial analysis cover scenario modeling, revenue and margin reconciliation, and reconciliation review, since these steps are most sensitive to inconsistent assumptions. Start with the six featured above, then add sector or company specific skills as your workflow matures.
Are the Claude finance skills free?
Yes, the full pack on this page is free to download. It includes work-order templates and setup guidance so you can put the skills to use for valuation, FP&A, and board reporting at no cost.