tidy
GitHub批量整理未分类交易。通过聚类相似交易、搜索商户信息，建议分类和对方名称。优先创建规则以自动处理未来交易，对单次交易直接标注，最终向用户汇报结果。
触发场景
安装
npx skills add davepoon/buildwithclaude --skill tidy -g -y
SKILL.md
Frontmatter
{
"name": "tidy",
"description": "Triggered by \"tidy up\", \"clean up transactions\", \"categorize uncategorized\", \"organize my transactions\""
}
Tidy Up Uncategorized Transactions
Batch-categorize uncategorized transactions by clustering similar ones and applying categories in bulk.
Workflow
-
Fetch uncategorized transactions. Call the
queryMCP tool:{ "detail": true, "is_uncategorized": true, "period": "last_90d", "limit": 200, "sort": "-amount" }If
$ARGUMENTScontains a time period (e.g. "this month", "last 30 days"), use that instead oflast_90d. -
Research unknown transactions. For transactions you can't identify from the description alone:
- Web search first (if available): Search for the merchant name, any phone numbers or domains in the description, or the raw description itself. This often reveals the business behind cryptic processor names.
- Search the user's email (if available): Search for the party/merchant name to find order confirmations or receipts. If that doesn't match, search for the exact dollar amount (e.g. "$47.23") to find receipts that way.
-
Cluster by pattern. Group the results by normalized description or party name. For each cluster, note the count and total amount.
-
Suggest categorization. For each cluster, propose:
- A category (pick from the user's existing categories)
- A party name (the clean merchant/counterparty name)
-
Present to the user. Show a table or list of clusters with:
- Pattern / merchant name
- Count of transactions
- Total amount
- Suggested category
- Whether you recommend creating a rule
Ask the user to approve, modify, or skip each cluster.
-
Prefer rules over one-off annotations. If a cluster has more than one transaction, or the merchant is likely to appear again (subscriptions, regular stores, utilities, etc.), create a rule rather than annotating individual transactions. Rules automatically categorize future transactions too.
- Preview first:
admin { "entity": "rule", "action": "preview", ... } - Show the preview (how many existing transactions would match)
- If user confirms, create:
admin { "entity": "rule", "action": "create", ... }
- Preview first:
-
Annotate the rest. For truly one-off transactions where a rule wouldn't help, apply directly:
{ "action": "categorize", "filter": { "search": "<pattern>" }, "category_name": "<approved_category>" }Also set the party if one was approved:
{ "action": "set_party", "filter": { "search": "<pattern>" }, "party_name": "<approved_party>" } -
Summarize. Report how many transactions were categorized, how many rules were created, and how many uncategorized transactions remain.
Tone
Stick to the facts. Present findings and suggestions without judgement — no commentary on spending habits. Just clear, plain-language observations and actionable options.
版本历史
- 502fc01 当前 2026-07-05 15:09
