openclaw-skill-personal-finance_skill

This skill parses personal finance CSV exports, validates schema, categorizes transactions with local rules, and summarizes income, expenses, and merchants.
  • Python

2.5k

GitHub Stars

4

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill openclaw-skill-personal-finance

  • _meta.json299 B
  • personal-finance.sh11.2 KB
  • README.md3.3 KB
  • SKILL.md2.5 KB

Overview

This skill parses personal finance CSV exports, validates their schema, categorizes transactions with local rules, and produces summarized reports of income, expenses, merchants, and categories. It operates offline and is read-only by default, masking account numbers in all outputs to protect PII. The workflow is simple: validate input, categorize with configurable rules, then summarize or report results.

How this skill works

The tool reads a CSV containing date, description, amount, and account_number fields and first validates schema and numeric amounts to catch export changes. It applies a local JSON rules file to map transaction descriptions to categories using keyword matching, and masks account numbers except the last four digits in any displayed output. Summaries aggregate positive amounts as income and negative amounts as expenses by month, quarter, or year; reports highlight top merchants and categories by spend.

When to use it

  • Before processing a new bank or card export to detect schema drift.
  • When you need an offline, auditable transaction categorization run.
  • To generate period summaries of income, expenses, and net flow.
  • To discover top merchants and categories by spend without cloud services.
  • When you want a CSV output with categories added for downstream tools.

Best practices

  • Run validate first to ensure the CSV has required fields and numeric amounts.
  • Keep the category-rules JSON tuned to your merchant vocabulary for accurate mapping.
  • Use the read-only default; provide an explicit output path only when you want a new CSV written.
  • Review masked account snippets to confirm data alignment without exposing PII.
  • Use month/quarter/year periods consistently when comparing multiple exports.

Example use cases

  • Validate a newly downloaded credit-card export quickly to confirm format.
  • Categorize historical transactions locally to build a budget dataset.
  • Summarize monthly income vs. expenses to spot cashflow trends.
  • Generate a report of top merchants and categories to identify spending hotspots.
  • Produce a categorized CSV to import into a budgeting app that accepts CSVs.

FAQ

No. All logic runs locally using the included script and rules file; it never performs external API calls.

How is sensitive account data protected?

Account numbers are masked in all CLI outputs by replacing digits except the final four; files are only written when you pass an explicit output path.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational