money_tracker#

Overview#

Use this skill for local bookkeeping with a lightweight SQLite database. Interpret the user's Chinese prompt, map it to a structured record or query, and use the bundled script to persist and analyze data.

Runtime Rules#

• Use python 3.9+ only. The bundled script uses only the standard library.
• Use UTF-8 and LF for all text inputs and outputs.
• Prefer the bundled script instead of writing ad-hoc SQL.
• Always reference bundled files via {baseDir} so the skill still works when installed under an OpenClaw skills/ directory.
• The uploaded runtime only needs {baseDir}/scripts/bookkeeping.py.
• Use the default database path unless the user explicitly wants a custom location.
• Default database path: ~/.money_tracker/bookkeeping.db
• Allow override with --db or the MONEY_TRACKER_DB environment variable.
• The bundled script also accepts the legacy LOCAL_BOOKKEEPING_DB environment variable and can fall back to the legacy ~/.local-bookkeeping/bookkeeping.db path when needed.
• Day, week, month, and year report commands do not perform FX conversion; mixed-currency periods are reported as raw stored amounts.
• For extra Chinese prompt examples, load {baseDir}/references/chat_reference.md only when needed.

Intent Routing#

Route the user's request into one of these flows:

1. 记账 ... or other natural-language add-entry requests
2. Category management such as setting, replacing, adding, listing, or deleting categories
3. Account management such as listing, enabling, resetting, updating, or deleting wallet accounts like 支付宝:CNY, 微信:CNY, 银行卡:USD, or Wise:EUR
4. Account balance queries such as 显示所有账户余额, 列出每个钱包余额, 我现在还有多少美元, or 我的欧元钱包还有多少
5. Recurring transaction management such as adding, listing, updating, or deleting periodic payments or income schedules
6. Day, week, month, or year totals such as 今天花了多少, 这周花了多少, 这个月花了多少, or 今年花了多少
7. Day, week, month, or year analysis such as 这周花销哪里更多, 这个月花销哪里更多, or 今年收入主要来自哪里
8. Day, week, month, or year detail queries such as 列出 2026-03-15 的账单, 列出这周的账单, 列出我这个月的账单, or 列出 2026 年的账单
9. Recent transaction queries such as 展示出最新的10个账单
10. Latest-entry queries such as 显示最近的一笔账
11. Update requests such as 修改一笔账 1 金额为12元，分类为学习
12. Deletion requests such as 删除一笔账 3 or 删除最近的一笔账

If the user's wording is relative, resolve it into an explicit date, week, month, or year before calling the script. In final answers, mention the exact period used, for example 2026-03-15, 2026-W11, 2026-03, or 2026.

Recording Workflow#

When the user asks to record a transaction:

1. Extract:
   • entry_type: default to expense; use income only when the prompt clearly indicates inflow such as salary, refund, reimbursement, bonus, or revenue.
   • amount: parse the positive numeric amount.
   • occurred_on: use YYYY-MM-DD; default to today if the prompt does not specify a date.
   • account: map to a wallet account such as 支付宝:CNY, 微信:CNY, 银行卡:CNY, 银行卡:USD, 银行卡:EUR, or another wallet like Wise:USD; use 未指定账户 only when the user did not specify one.
   • description: keep it short and concrete, such as 奶茶, 英语教材, 插线板.
   • note: keep extra context only if useful.
   • source_text: store the original natural-language prompt when practical.
2. Load the active categories first with list-categories.
3. Load the active accounts first with list-accounts if the account matters and you do not already know which ones are active.
4. If active categories exist, map the transaction into exactly one of them using semantic judgment.
5. If the mapping is clear, record with --strict-category.
6. If the account is clear and active, record with --strict-account.
7. If no categories exist yet, or the mapping is not reliable, either:
   • ask the user to define categories, or
   • record the transaction as 未分类 without --strict-category.
8. After writing the record, report the saved amount, category, account, date, and whether the category and account matched predefined values.

Category Rules#

• Categories are user-defined flat labels such as 日常, 学习, 电器.
• Use set-categories --replace when the user wants to redefine the whole active category set.
• Use set-categories without --replace when the user wants to add more categories while preserving existing ones.
• Use list-categories before classification if you do not already know the active category set from the current conversation.
• If multiple categories are plausible, ask one disambiguation question instead of guessing.
• For 显示分类, call list-categories.
• For 添加分类 ..., call set-categories without --replace.
• For 删除分类 ..., call delete-category --name <category> and treat it as deactivation, not history rewrites.

Account Rules#

• Accounts are wallet-style records with both a wallet name and a currency.
• Default wallets are seeded automatically when the database is initialized:
  • 支付宝:CNY
  • 微信:CNY
  • 银行卡:CNY
  • 银行卡:USD
  • 银行卡:EUR
• Custom wallets are allowed, for example Wise:USD, Revolut:EUR, or PayPal:USD.
• Use list-accounts to inspect the active wallet set.
• Use account-balances when the user asks about balances by wallet or totals by currency.
• For questions about current holdings such as "how much USD do I have now", prefer account-balances over a period report.
• Use set-accounts --replace when the user wants to reset the whole active wallet set.
• Use set-accounts without --replace when the user wants to re-enable or add more wallets while preserving existing ones.
• Use update-account --name <wallet:currency> ... when the user wants to rename a wallet or change its configured currency.
• If the user specifies a wallet without a currency:
  • use the wallet's default currency when one exists, such as 支付宝 -> CNY or 银行卡 -> CNY
  • otherwise require a currency, such as Wise:USD
• When recording or updating an entry, the final entry currency must match the selected wallet currency.
• update-account propagates the new wallet label and currency to linked entries and recurring schedules for consistency.
• For 删除账户 ..., call delete-account --name <wallet:currency> and treat it as deactivation, not history rewrites.

Recurring Workflow#

Use recurring transactions to store scheduled payments or income that repeat over time.

When the user asks to manage recurring transactions:

1. Extract:
   • entry_type: default to expense unless the recurring item is clearly income.
   • amount
   • category
   • account
   • description
   • frequency: one of weekly, monthly, or yearly
   • interval: default to 1
   • next_due_on: use YYYY-MM-DD
2. For creation, run add-recurring ....
3. For listing schedules, run list-recurring.
4. If the user wants to include inactive schedules too, run list-recurring --all.
5. If the user wants to see only items due by a specific date, run list-recurring --due-by YYYY-MM-DD.
6. For updates, require an id and run update-recurring --id <id> ....
7. For explicit activation or deactivation, use update-recurring --id <id> --activate or update-recurring --id <id> --deactivate.
8. For deletion-style wording, require an id and run delete-recurring --id <id> as a deactivation shortcut.

Example prompts:

• 添加周期性支出 每月 1 号交房租 3000 用银行卡
• 添加周期性支出 每周交健身房 100 用微信
• 列出所有周期性账单
• 列出本月到期的周期性账单
• 修改周期性账单 1 下次日期为 2026-05-01
• 删除周期性账单 2

Query Workflow#

For account balance queries:

1. If the user wants balances by wallet or totals by currency, run account-balances.
2. If the user asks about one currency only, pass account-balances --currency <CODE>.
3. Answer from:
   • accounts for each wallet balance
   • totals_by_currency for grouped totals such as total CNY, total USD, and total EUR

Example prompts:

• 显示所有账户余额
• 列出每个钱包余额
• 我现在还有多少美元
• 我的欧元钱包还有多少

For day, week, month, or year totals or analysis:

1. Resolve the target period to one of:
   • YYYY-MM-DD for a day
   • YYYY-Www for an ISO week
   • YYYY-MM for a month
   • YYYY for a year
2. Run the matching report command:
   • day-report --date YYYY-MM-DD
   • week-report --week YYYY-Www
   • month-report --month YYYY-MM
   • year-report --year YYYY
3. Answer from the structured result:
   • expense_total for total spending
   • income_total for total income
   • net_total for net cash flow
   • expense_by_category for where spending is concentrated
   • top_expense_category for the largest spending category
   • expense_by_account for which account handled the spending
   • top_expense_account for the most-used spending account in the selected period
4. If the selected period contains more than one currency, explicitly say the totals are raw stored amounts and no FX conversion was applied.
5. For "how much money do I have now by currency" questions, do not use these period report commands; use account-balances instead.

Example prompts:

• 今天花了多少
• 2026-03-15 花了多少
• 这周花了多少
• 2026-W11 花了多少
• 这个月花了多少
• 2026-03 花了多少
• 今年花了多少
• 2026 年花了多少
• 这周花销哪里更多
• 今年收入主要来自哪里

For detail queries:

1. Resolve the target period.

2. If the user asks for a category filter, load active categories first and pass --category <name>.

3. If the user asks for an account filter, load active accounts first and pass --account <wallet:currency> when the currency matters.

4. Run list-transactions with exactly one period selector:

   • --date YYYY-MM-DD
   • --week YYYY-Www
   • --month YYYY-MM
   • --year YYYY

5. Summarize or list the returned entries.

Example prompts:

• 列出 2026-03-15 的账单
• 显示今天的账单
• 列出这周的账单
• 列出 2026-W11 的账单
• 列出这个月的账单
• 列出 2026-03 的账单
• 列出今年的账单
• 列出 2026 年的账单
• 列出 2026-03-15 学习分类的账单
• 列出 2026-03 的支付宝账单
• 列出 2026-03 的银行卡美元账单

For latest-entry queries:

1. Run latest-entry.
2. Return the saved entry id, date, amount, category, account, and description.

For recent-entry queries:

1. Parse the requested count; default to 10 if the user asks for latest without a number.
2. If the user asks for a category filter, load active categories first and pass --category <name>.
3. If the user asks for an account filter, load active accounts first and pass --account <wallet:currency> when the currency matters.
4. Run recent-transactions --limit N.

For updates:

1. Require an id for either an entry or a recurring transaction.
2. Extract only the fields the user explicitly wants to change.
3. If the category is being changed, validate it against the active category list when possible.
4. If the account is being changed, validate it against the active account list when possible.
5. Use update-entry --id <id> ... for transactions.
6. Use update-recurring --id <id> ... for recurring schedules.

For deletion:

1. If the user asks for the latest entry, run delete-latest-entry.
2. If the user asks to delete a specific entry, require an id and run delete-entry --id <id>.
3. If the user asks to delete a recurring schedule, require an id and run delete-recurring --id <id>.
4. If no id is provided, ask for it instead of guessing.

Script Entry Points#

Use {baseDir}/references/commands.md for exact runtime command shapes. Use {baseDir}/references/chat_reference.md only when you need extra natural-language prompt examples.

Main commands:

• python "{baseDir}/scripts/bookkeeping.py" init-db
• python "{baseDir}/scripts/bookkeeping.py" list-categories
• python "{baseDir}/scripts/bookkeeping.py" list-accounts
• python "{baseDir}/scripts/bookkeeping.py" account-balances
• python "{baseDir}/scripts/bookkeeping.py" account-balances --currency USD
• python "{baseDir}/scripts/bookkeeping.py" set-categories --replace 日常 学习 电器
• python "{baseDir}/scripts/bookkeeping.py" set-accounts --replace 支付宝:CNY 微信:CNY 银行卡:CNY 银行卡:USD 银行卡:EUR
• python "{baseDir}/scripts/bookkeeping.py" update-account --name Wise:USD --new-name TravelCard --currency EUR
• python "{baseDir}/scripts/bookkeeping.py" set-categories 旅行
• python "{baseDir}/scripts/bookkeeping.py" record --amount 10 --category 日常 --account 支付宝 --description 奶茶 --date 2026-03-15 --source-text "我喝奶茶用了10元" --strict-category --strict-account
• python "{baseDir}/scripts/bookkeeping.py" record --amount 12 --category 订阅 --account 银行卡:USD --description Claude --date 2026-03-15 --strict-account
• python "{baseDir}/scripts/bookkeeping.py" add-recurring --amount 3000 --category 日常 --account 银行卡:CNY --description 房租 --frequency monthly --next-date 2026-04-01 --strict-category --strict-account
• python "{baseDir}/scripts/bookkeeping.py" list-recurring --all
• python "{baseDir}/scripts/bookkeeping.py" list-recurring --due-by 2026-04-30
• python "{baseDir}/scripts/bookkeeping.py" day-report --date 2026-03-15
• python "{baseDir}/scripts/bookkeeping.py" week-report --week 2026-W11
• python "{baseDir}/scripts/bookkeeping.py" month-report --month 2026-03
• python "{baseDir}/scripts/bookkeeping.py" year-report --year 2026
• python "{baseDir}/scripts/bookkeeping.py" list-transactions --date 2026-03-15 --account 支付宝
• python "{baseDir}/scripts/bookkeeping.py" list-transactions --month 2026-03 --account 银行卡:USD
• python "{baseDir}/scripts/bookkeeping.py" list-transactions --month 2026-03
• python "{baseDir}/scripts/bookkeeping.py" recent-transactions --limit 10 --account 微信
• python "{baseDir}/scripts/bookkeeping.py" latest-entry
• python "{baseDir}/scripts/bookkeeping.py" update-entry --id 1 --amount 12 --category 学习 --account 微信 --description 奶茶教材 --strict-category --strict-account
• python "{baseDir}/scripts/bookkeeping.py" update-recurring --id 1 --account 银行卡:USD --next-date 2026-05-01 --strict-account
• python "{baseDir}/scripts/bookkeeping.py" update-recurring --id 1 --deactivate
• python "{baseDir}/scripts/bookkeeping.py" update-recurring --id 1 --activate
• python "{baseDir}/scripts/bookkeeping.py" delete-entry --id 3
• python "{baseDir}/scripts/bookkeeping.py" delete-latest-entry
• python "{baseDir}/scripts/bookkeeping.py" delete-category --name 旅行
• python "{baseDir}/scripts/bookkeeping.py" delete-account --name 银行卡:USD
• python "{baseDir}/scripts/bookkeeping.py" delete-recurring --id 2

Response Rules#

• Keep the user-facing response concise.
• When recording an entry, mention the exact date used.
• When answering an account balance query, mention both the wallet balances and the grouped totals by currency when relevant.
• When answering a day, week, month, or year query, mention the exact period used.
• When a report period contains more than one currency, say plainly that the totals are raw amounts and no FX conversion was applied.
• If the script reports an unmatched category or unmatched account, say so plainly and suggest updating the active sets if needed.
• If the database is empty for the requested period, state that directly.