Personal Finance Tracker
v1.0.0Manage personal finances, track spending by category, set budgets, and receive reminders for EMIs and one-time annual expenses. Use for logging expenses, checking budget status, or setting up financial reminders.
⭐ 6· 3.8k·23 current·24 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (personal finance tracking, budgets, reminders) matches the provided files and instructions. The included init_db.py and SKILL.md only create and use a local SQLite DB; there are no unrelated env vars, binaries, or cloud credentials requested.
Instruction Scope
SKILL.md limits actions to initializing and using finance.db and summarizing transactions / checking schedules. It mentions scheduled reminders but does not specify delivery mechanism; that is a minor vagueness (not evidence of exfiltration) — confirm how reminders are delivered by the agent before enabling automated notifications.
Install Mechanism
No install spec; this is instruction-only plus a small init_db.py script. The script only creates directories and a local SQLite DB under the skill workspace. No downloads or external installers are used.
Credentials
The skill declares no required environment variables, credentials, or config paths. The code also does not read env vars or attempt to access system credentials — storage is local to ~/.openclaw/workspace/skills/personal-finance/finance.db.
Persistence & Privilege
always is false and model invocation is allowed (platform default). The skill writes its own local DB but does not modify other skills or system-wide settings. Autonomous invocation is not combined with any broad credential access, so no elevated privilege concerns.
Assessment
This skill appears to do what it says: it stores data locally in ~/.openclaw/workspace/skills/personal-finance/finance.db and contains a small init script that creates tables and preset categories. Before installing, consider: 1) where the DB will be stored and whether you want financial data in that path (move or encrypt it if needed), 2) how the agent will deliver reminders (email/Slack/notifications)—ensure those channels are acceptable because the agent could include sensitive ledger data in messages, 3) review or run init_db.py yourself to verify behavior, and 4) back up or export data if you need persistence outside the skill workspace. Also note a minor DB oddity: schedules.name is declared a foreign key referencing categories(name) (unusual but not harmful). Overall no network calls or credential requests were found.Like a lobster shell, security has layers — review code before you run it.
latestvk9769krd1fcm89c31n7na6xbpx80jztx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.