Reconcile Transactions Across Your Accounts

Reconcile transactions across your accounts — skill template

Turn this template into a working skill by resolving every TODO. The seed prompt below is the published Anthropic example this template was derived from; your skill should generalize it for repeated, hands-off use.

Outcome

Hand Cowork your bank exports and ledger files. It matches transactions across sources, flags discrepancies, and outputs an annotated reconciliation report.

TODO: Restate the outcome for YOUR context in one sentence: who runs this, on what input, producing what artifact, how often.

Seed prompt (verbatim from source, © Anthropic PBC)

I need to reconcile my January 2024 bank statement. I've uploaded my checking account statement export and my current chart of accounts. Can you analyze the transactions, match them to the right accounts, and flag anything that doesn't line up? If there are discrepancies, I'd love journal entries to fix them.

Required context and inputs

• Claude Desktop app
• Cowork feature
• Bank statement export file
• Chart of accounts file
• TODO: exact file paths / folders / message formats this skill should expect
• TODO: domain context the model cannot infer (naming conventions, thresholds, house style)

Tools, connectors, APIs, and authentication

• No connectors detected on the source page; base Claude capabilities only
• TODO: confirm which connectors are enabled in the runtime that will execute this skill
• Authentication: connectors authenticate via their own OAuth flows — this skill must

NEVER ask for, store, or echo credentials, tokens, or API keys. If auth is missing, stop and tell the user which connector to enable.

Permissions and sensitive actions

• Reads: TODO (folders, channels, records this skill may read)
• Writes: TODO (what it may create/modify, and where)
• Held back for the primary agent / human: sending external communications, financial

transactions, deleting or overwriting originals, submitting web forms

Workflow

1. Download Claude Desktop and start a Cowork session
2. Select "Work in a folder" to give Cowork access to financial files, or use the "+" button to add individual files
3. Claude analyzes both files, matches transactions to accounts, and surfaces discrepancies
4. Review matching results (percentages matched, items needing categorization, discrepancies identified)
5. Export journal entries as CSV or create reconciliation summaries as needed

TODO: adapt the steps above (from the source page) into imperative instructions for the executing agent, including what to do between steps.

Decision points

• TODO: list each point where the skill must choose between paths, with the rule to apply
• Default rule: prefer the reversible option; when two readings of the input are

plausible, surface both rather than picking silently.

Validation criteria

• Output matches the outcome statement above (spot-check against the seed prompt's asks)
• Every factual claim is traceable to a provided input, connector record, or cited source
• All figures reconcile to source statements/workbooks; totals recomputed programmatically, not by eye
• Flag (never silently correct) discrepancies between model and source data
• TODO: add one domain-specific check a reviewer in your org would apply

Failure modes and fallbacks

• Expected files missing from the connected folder → list what was found, ask before proceeding on partial inputs
• Ambiguous or missing input → ask one targeted question; if unattended, state the assumption inline and proceed
• Any step would take a sensitive/irreversible action → stop and hand back to the user (see Delegation)

Delegation

Apply the repo's delegation policy (docs/delegation-policy.md — bundle or restate it if you install this skill outside the repo). Defaults for this template:

• Run single-agent unless a step fans out over independent items (files, records,

vendors, channels). Only independent work parallelizes.

• Each delegated task must ship with: the minimal context slice it needs, an explicit

output contract, a validation check the primary agent runs on the result, and a fallback if it returns empty or fails.

• Final review, synthesis, and every sensitive action listed above stay with the

primary agent.

• TODO: name the concrete subtasks (if any) that qualify for delegation here.

Attribution

Derived from Reconcile transactions across your accounts (retrieved 2026-07-26). Seed prompt and workflow content © Anthropic PBC. Scaffold structure original to this repository.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: iankiku
• Source: iankiku/agent-skill-factory
• License: MIT

Install and usage instructions live in the source repository linked above.