Beancount
v2.0.0Personal bookkeeping assistant for local income and expense tracking, monthly reports with comparisons, budget alerts, and savings goal management.
⭐ 0· 274·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
SKILL.md and scripts/book.sh align: personal bookkeeping, local JSON storage in ~/.bookkeeping, commands implemented in scripts/book.sh. One extra companion script (scripts/script.sh) is included that uses a different data directory (~/.local/share/beancount) and provides a generic CLI; it is not referenced by the SKILL.md commands. The extra script is likely benign but unnecessary and should be noted.
Instruction Scope
Runtime instructions (SKILL.md) say data is stored locally and scripts/book.sh only reads/writes files under the user's home (~/.bookkeeping). There are no network calls, no reads of unrelated system files, and no access to credentials in the provided code.
Install Mechanism
No install spec; this is an instruction+script bundle. No downloads or archive extraction are present in the package, so nothing is written to disk beyond the included files and the data files the scripts deliberately create.
Credentials
The skill declares no required environment variables or credentials. The scripts respect common environment conventions: scripts/script.sh will honor BEANCOUNT_DIR or XDG_DATA_HOME if set, and both scripts expand $HOME for data storage. That use is reasonable and optional, not required.
Persistence & Privilege
always is false and the skill does not modify other skills or system-wide settings. It creates and writes its own data files under the user's home directory only.
Assessment
This skill implements a local bookkeeping tool and appears to do only local file read/write in your home directory. Before installing: (1) review and trust the source (files include an extra scripts/script.sh that is not referenced by SKILL.md), (2) be aware it will create ~/.bookkeeping/records.json, budgets.json, goals.json (and scripts/script.sh may use ~/.local/share/beancount), (3) if your records are sensitive consider encrypting/backing up those files or placing them in an encrypted directory, and (4) if you don't need the extra scripts, remove them after inspection. If you want higher assurance, ask the maintainer for provenance (commit history or release page) or run the scripts in a sandbox first.Like a lobster shell, security has layers — review code before you run it.
latestvk97b91c24sy3xrqsqym98dzbvs833pjr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.