Make a local spending dashboard from bank exports
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and make a local spending dashboard from bank exports.
LLMPrompt
Prompt
Copied 0
Build me a private spending dashboard. Work only in this folder: [path]. Do not upload my data anywhere, and do not install anything without asking. Inputs (read only, never edit these files): - CSV exports: [bank-checking.csv, card-1.csv, card-2.csv], covering [months]. - Statement totals to check against: [account: total out, total in, for each month]. 1. Write a script (Python or similar) that loads every CSV. Print, for each file, the column names, the row count, the first and last date, and the sums of money in and money out. Every number must come from the code, not from you. 2. STOP. Show me those numbers next to my statement totals and wait for me. 3. Mark lines that are not spending: transfers between my own accounts, credit card payments, refunds. List them and wait for my OK, so nothing is counted twice. 4. Propose a rules file, categories.csv, that maps payee text to a category from this list: [Housing, Groceries, Eating out, Transport, Subscriptions, Health, Shopping, Travel, Other]. Show me the 30 biggest payees and the rule for each. Wait for me to edit and approve it. 5. Apply the rules. Put anything without a rule under "Uncategorised" and list it. Do not guess. 6. Build one local HTML file with charts: spending by month, by category, top payees, and a table I can filter. Show the check totals at the top. 7. Write a short README that explains how to rerun it next month with new CSVs.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/spending-dashboard-agents-handbook - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "spending-dashboard-agents-handbook",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}