agentleFS
Sign inStart free
codewhale-hqcodewhale-hq/codewhale-plugin-marketplace/skills/money/SKILL.md

money

Skill5 starsChanged 18 days agoMITView on GitHub

Bank accounts, balances, and transactions via Plaid. Use when: bank, balance, transactions, spending, accounts, or plaid.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not move money, pay bills, or initiate transfers.

    line 32
  2. Distinctive:

    Do not store account or routing numbers beyond the session need.

    line 33
  3. Distinctive:

    Do not paste secrets into chat, logs, or files.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Money

When to use

Account balances, transaction history, and spending analysis across the user's bank accounts.

Setup

Requires Plaid API credentials. Fail loud when they are missing:

PLAID_CLIENT_ID=... PLAID_SECRET=...  # sandbox keys first, production only when asked

The Link flow opens in the user's browser — the user completes it, the agent drives everything after token exchange. Start in sandbox; touch production only with explicit approval.

Workflow

  1. Exchange the public token once: POST /item/public_token/exchange.
  2. Balances: POST /accounts/balance. History: POST /transactions/sync with its cursor, paging until has_more is false.
  3. Report with dates, merchant names, and amounts; call out pending vs posted.
  4. Spending analysis aggregates by category or merchant on request.

Non-goals

  • Do not move money, pay bills, or initiate transfers. Read-only, always.
  • Do not store account or routing numbers beyond the session need.
  • Do not paste secrets into chat, logs, or files.

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.

Check your setup, free