agentleFS
bankbridge-moneybankbridge-money/bankbridge-skills/tax-prep-assistant/SKILL.md

tax-prep-assistant

Skill0 starsChanged 17 days agoMITView on GitHub

Export a full year of transactions grouped by category, with subtotals, for bookkeeping or tax filing. Produces a CSV file and a plain-text summary. Use when the user asks to prep for taxes, export for their accountant, or get a year-end summary.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Identify the year: If the user names one ("2025"), use that.

    line 20
  2. Very specific:

    Pull all transactions: Call list_transactions with start_date: <year>-01-01, end_date: <year>-12-31, limit: 100, paginating via offset …

    line 22
  3. Very specific:

    Pull category breakdown: Call get_spending_summary with the same date range, grouped by category.

    line 24
  4. Distinctive:

    Do not claim tax deductibility: Only an accountant can make that call.

    line 63
  5. Distinctive:

    Use exact amounts with 2 decimals.

    line 64
  6. Distinctive:

    If BankBridge's transactions are missing (account wasn't connected for part of the year, or the bank was disconnected), say so directly: …

    line 66
  7. Distinctive:

    Never sign / commit to a deduction.

    line 70
  8. Distinctive:

    Don't estimate. If BankBridge returned 0 results for a window, say 0 and don't extrapolate.

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Tax prep assistant

You have access to BankBridge MCP tools AND code execution. The user wants to organize a year's worth of transactions into a format their accountant or tax software can ingest.

When to use

Trigger on:

  • "help me prep for taxes"
  • "export everything from 2025 for my accountant"
  • "year-end transaction summary"
  • "total my Uber spending last year" (narrower variant)

Process

  1. Identify the year. If the user names one ("2025"), use that. Otherwise default to the most recently completed calendar year.
  2. Pull all transactions. Call list_transactions with start_date: <year>-01-01, end_date: <year>-12-31, limit: 100, paginating via offset until has_more: false. Collect everything.
  3. Pull category breakdown. Call get_spending_summary with the same date range, grouped by category.
  4. Generate a CSV. Columns, in order:
date, merchant, name, amount, category, category_detailed, account_type, institution, pending

One row per transaction. Sort by date ascending. Use standard CSV quoting for fields that contain commas or quotes. Save as bankbridge-<year>.csv in the working directory.

  1. Generate a plain-text summary. Format:
# Tax-year summary: <year>

## Totals
- Total outflow (expenses):    $XX,XXX.XX    (N transactions)
- Total inflow (income):       $XX,XXX.XX    (N transactions)
- Net:                         $XX,XXX.XX

## By category (outflow only, descending)
| Category | Total | Count | Avg |
|---|---|---|---|

## Potentially deductible (review with accountant)
Surface (without claiming deductibility):
  - HOME_IMPROVEMENT
  - MEDICAL (any medical/dental/vision)
  - EDUCATION
  - GENERAL_SERVICES_SUBSCRIPTIONS matching business-software terms (GitHub, Claude Pro, Notion, etc.)
  - TRANSPORTATION that pattern-matches business travel
Format: "<category>: $X,XXX across N transactions, review with your accountant"

## Files written
- bankbridge-<year>.csv  (full transaction export)

Style

  • Do not claim tax deductibility. Only an accountant can make that call; you're surfacing candidates, not making determinations.
  • Use exact amounts with 2 decimals. Taxes need precision.
  • Clearly distinguish income from expenses.
  • If BankBridge's transactions are missing (account wasn't connected for part of the year, or the bank was disconnected), say so directly: "Chase credit card was disconnected from Feb 3 – Mar 15; activity during that window isn't included."

Guardrails

  • Never sign / commit to a deduction. Use language like "potentially deductible" or "worth discussing with your accountant."
  • Don't estimate. If BankBridge returned 0 results for a window, say 0 and don't extrapolate.
  • Point the user to a real CPA for anything beyond categorization. You're assembly; they're interpretation.
  • The CSV file goes into the user's working directory. Tell them where it is.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.