Top 10 Claude Skills for CFOs and Finance Teams

"Claude skills" is having a moment in finance search right now, and most of what shows up for the query is generic: a list of writing and productivity skills with an accounting example bolted on for relevance. That list is accurate as far as it goes. It stops well short of the workflow-specific half of the answer for someone running a close.

Skills for Claude split into two kinds once you're doing accounting work with them. The first kind is general-purpose: built for any knowledge worker, genuinely useful for finance, and worth turning on regardless of what else you run. The second kind is built for the accounting workflow specifically, with the inputs, matching logic, and reviewable output that a general skill was never designed to produce. This list covers five of each, in the same packaged-skill format Claude uses, so you know which pile you're pulling from before you rely on the output.

---

What a "skill" actually is, in one paragraph

A Claude skill is a packaged set of instructions, and sometimes supporting files or tools, that Claude loads for a specific kind of task instead of you re-explaining the task in every conversation. Anthropic ships several built in. Anyone, including a vendor like Adopt, can build one for a narrower job and hand it to Claude the same way. The format is shared, which is the useful part for finance: a skill built for reconciliation work is a skill, exactly like a skill built for editing a spreadsheet, and it can move between systems that speak the same format instead of being locked to one vendor's app.

---

5 general Claude skills every finance team should already be running

None of these were built for accounting. All five show up constantly in the close, the board deck, and the inbox anyway.

1. Excel (xlsx)

Builds and edits real spreadsheet files: formulas, formatting, multiple tabs, charts, not a flattened export of one. Useful for anything you'd otherwise hand-build in Excel after pulling numbers from somewhere else: a variance schedule, a covenant tracker, a first pass at a model. It has no built-in accounting logic and no idea what your chart of accounts means. It formats the workbook. You still own the numbers going into it.

2. PowerPoint (pptx)

Turns a set of numbers and talking points into an actual deck, not a wall of bullet text. The obvious use is the board package: once the flux commentary and the KPI page exist somewhere, this skill is what turns them into slides without a night spent in PowerPoint. Same caveat as Excel: it formats and drafts, it doesn't verify that the underlying figures tie out.

3. Word (docx)

Drafts and edits real Word documents with formatting intact, which matters for anything that has to leave your desk looking finished: a close memo, a policy write-up, a variance explanation an auditor will read closely. Someone on your team still reads it before it goes out.

4. PDF

Reads and extracts from PDF files, which in finance means bank statements, vendor invoices, and signed agreements that never had structured data behind them in the first place. This is the single most useful general skill for accounting work specifically, because so much of the source documentation in a close still arrives as a PDF and nothing else. It reads one document at a time, on request. It doesn't sit connected to an inbox pulling every statement down automatically, and it doesn't apply your matching rules to what it finds.

5. Canva

Design software connected to Claude for anything that needs to look like a finished, on-brand asset rather than a plain document: a one-page investor update, an internal chart for a town hall, a polished version of a board slide. Not an accounting tool by any stretch, but the fastest way to make a number look like it's ready for someone outside the finance team to see.

The pattern across all five: they're excellent at producing a well-formatted document from information you already have. None of them retrieve that information from a bank portal, apply matching logic, or know what a reconciling item is. That's the gap the next five are built to close.

---

5 skills built specifically for close, reconciliation, and reporting

These are skills Adopt has built for finance workflows, packaged in the same format as the five above and portable the same way: they can move to or from Claude directly instead of being locked into one interface. Each one takes a defined set of finance inputs, applies the logic a preparer would apply by hand, and hands back a reviewable draft, never a posted, final answer. A person still approves the output before it counts.

6. Flux Narrative Builder

Computes period-over-period movement from two trial balances, applies your dollar and percent thresholds, and drafts a variance explanation with the source line attached, for a reviewer to edit rather than write from scratch. Built for the day-one-flux problem: getting a first draft of variance commentary out before the close has even finished, instead of assembling it by hand in week three.

7. Three-Way Match

Matches purchase orders to vendor invoices to receiving records: did the company order it, receive it, and get billed correctly for it. Checks quantities and prices against your tolerance policy, proves the full population ties to the AP subledger, and splits the result into clean matches, exceptions, duplicates, and goods received but not yet invoiced. Nothing pays or posts. A reviewer works the exception tab.

8. Bank Statement → Excel

Pulls the transaction detail out of a statement PDF, text-layer or scanned, into a workbook a preparer, reviewer, or auditor can rely on without reopening the PDF. Every row carries a source page reference, and the balance roll-forward has to tie out before the workbook counts as done. Built for the exact gap where a bank has no clean data feed and someone would otherwise be retyping a statement line by line.

9. Cash Flow Statement Tie-Out

Derives an indirect-method statement of cash flows straight from the balance sheet and income statement, then compares it line by line against whatever cash flow statement already exists. It catches a plug hiding inside an "other" caption instead of letting it pass, since every working-capital movement gets derived from the balance sheet rather than taken at face value.

10. Audit Workpaper

Builds a workpaper in the form an auditor expects: header block, objective, population and source, procedures performed, evidence examined, exceptions, and a conclusion. Then it checks that the conclusion actually matches what got documented, the one step most hand-built workpapers skip and a reviewer usually catches too late.

---

How to use these together

Don't pick one column and ignore the other. The general skills are the finishing layer: the deck, the memo, the polished export. The finance-built skills are the retrieval-and-matching layer: pulling the right numbers, applying the rules a preparer already knows, and handing back something specific enough to review in minutes instead of build from a blank sheet.

The discipline that makes any of this safe is the same one good finance teams already apply to a new hire: nothing posts, sends, or files without a human looking at it first. That's true of a general drafting skill formatting a memo, and it's true of a finance-built skill proposing an accrual. The output is a draft with its sources attached. The sign-off stays exactly where it already is.

---

Related reading

• How to Become an AI CFO: A 12-Month Roadmap
• The AI CFO Tech Stack: What Finance Leaders Are Actually Running in 2026

Glossary

• Record to Report (R2R) · Bank Reconciliation

---

Skill names, descriptions, and status reflect Adopt's own roadmap and general-purpose Claude skills as of this writing. Verify current availability before treating any single skill as generally available.