← Back to Skills Marketplace
ckchzh

Budgetly

by BytesAgain2 · GitHub ↗ · v2.0.1 · MIT-0
cross-platform ✓ Security Clean
346
Downloads
0
Stars
1
Active Installs
8
Versions
Install in OpenClaw
/install budgetly
Description
Set category budgets, log expenses, and visualize spending limits. Use when tracking grocery costs, monitoring subscriptions, or forecasting spend.
README (SKILL.md)

BudgetLy

BudgetLy v2.0.0 — a personal finance toolkit for recording expenses, categorizing spending, checking balances, analyzing trends, forecasting budgets, and generating reports from the command line.

Why BudgetLy?

  • Full-featured personal finance tracker with 12 specialized commands
  • No external dependencies, accounts, or API keys needed — your data stays local
  • All entries are timestamped and stored in plain-text log files
  • Export to JSON, CSV, or TXT for analysis in spreadsheets or other tools
  • Built-in search, statistics, and health-check utilities
  • Works on any system with Bash

Commands

Command Usage Description
record budgetly record \x3Cinput> Record a financial transaction or expense entry
categorize budgetly categorize \x3Cinput> Categorize a transaction (e.g., food, transport, rent)
balance budgetly balance \x3Cinput> Log or check account balance information
trend budgetly trend \x3Cinput> Log trend data for spending pattern analysis
forecast budgetly forecast \x3Cinput> Record a budget forecast or projection
export-report budgetly export-report \x3Cinput> Generate and log an export report entry
budget-check budgetly budget-check \x3Cinput> Check budget limits and log the result
summary budgetly summary \x3Cinput> Log a financial summary (daily, weekly, monthly)
alert budgetly alert \x3Cinput> Set or log a budget alert (overspend warnings, etc.)
history budgetly history \x3Cinput> Log or view financial history entries
compare budgetly compare \x3Cinput> Compare spending across periods or categories
tax-note budgetly tax-note \x3Cinput> Record tax-related notes and deductions
stats budgetly stats Show summary statistics across all log files
export budgetly export \x3Cfmt> Export all data (json, csv, or txt)
search budgetly search \x3Cterm> Search across all log files for a keyword
recent budgetly recent Show the 20 most recent history entries
status budgetly status Health check — version, entry count, disk usage
help budgetly help Show the help message with all commands
version budgetly version Print the current version

All entry commands (record, categorize, balance, trend, forecast, export-report, budget-check, summary, alert, history, compare, tax-note) work the same way:

  • With arguments: saves a timestamped entry to \x3Ccommand>.log and logs to history.log
  • Without arguments: displays the 20 most recent entries from that command's log

Data Storage

All data is stored in ~/.local/share/budgetly/:

  • record.log, categorize.log, balance.log, etc. — one log file per command
  • history.log — unified activity log across all commands
  • export.json / export.csv / export.txt — generated export files

Each entry is stored as YYYY-MM-DD HH:MM|\x3Cvalue> (pipe-delimited timestamp and content).

Requirements

  • Bash (with set -euo pipefail)
  • Standard Unix utilities: date, wc, du, grep, head, tail, cat
  • No external dependencies, no Python, no API keys

When to Use

  1. Daily expense logging — Use budgetly record "Lunch at cafe ¥45" to maintain a running log of daily expenses and review them later with budgetly record (no args shows recent entries).
  2. Category-based spending analysis — Use budgetly categorize "food: ¥2,300 this month" to organize expenses by category and then search with budgetly search "food" to analyze patterns.
  3. Monthly budget forecasting — Use budgetly forecast "April budget: rent ¥3000, food ¥2500, transport ¥800" to plan ahead and compare actuals later with budgetly compare.
  4. Tax preparation — Use budgetly tax-note "Home office deduction: ¥1,200/month, receipts in folder Q1-2026" to keep tax-related notes organized and export them with budgetly export csv.
  5. Spending alerts and limits — Use budgetly alert "Entertainment budget exceeded: ¥1,500/¥1,000 limit" to log overspend warnings and review alerts with budgetly alert.

Examples

# Record daily expenses
budgetly record "Coffee ¥15, lunch ¥42, groceries ¥128"
budgetly record "Monthly rent ¥3,500"

# Categorize spending
budgetly categorize "transport: Uber ¥30, subway ¥8, gas ¥200"
budgetly categorize "subscriptions: Netflix ¥45, Spotify ¥15, iCloud ¥6"

# Check and log balance
budgetly balance "Checking account: ¥15,230 as of March 18"

# Analyze spending trends
budgetly trend "Food spending up 15% vs last month"

# Forecast next month
budgetly forecast "April projection: total ¥8,500 (down from ¥9,200 in March)"

# Set budget alerts
budgetly alert "Warning: dining out already at 80% of monthly limit"

# Log tax-related items
budgetly tax-note "Charitable donation ¥500 to Red Cross, receipt #RC-2026-0318"

# Compare periods
budgetly compare "Q1 vs Q4: food +12%, transport -8%, entertainment -20%"

# View summary statistics
budgetly stats

# Search for specific entries
budgetly search "groceries"

# Export everything to JSON
budgetly export json

# Check system status
budgetly status

# View recent activity
budgetly recent

Configuration

Data directory: ~/.local/share/budgetly/ (hardcoded, no environment variable override).

Output

All commands print results to stdout. Redirect output to a file if needed:

budgetly stats > my-finance-stats.txt
budgetly export csv

Note: This is an original, independent implementation by BytesAgain. Not affiliated with or derived from any third-party project.


Powered by BytesAgain | bytesagain.com | [email protected]

Usage Guidance
This skill appears coherent and local-only, but take these precautions before installing: - Verify the full contents of scripts/script.sh (the supplied file listing in the prompt was truncated); confirm there are no network calls or unexpected commands in the parts not shown. The current visible script contains no network access. - Be aware all data is stored as plain-text under ~/.local/share/budgetly (hardcoded). If you're storing sensitive financial details, consider: restricting file permissions (chmod 700 ~/.local/share/budgetly), encrypting exports or using an encrypted filesystem, or modifying the script to allow a configurable data directory. - Back up data before running, and inspect the script for any command injection risks if you plan to pipe untrusted input into it. The implementation appears to append user-provided strings directly into log files — avoid running it on untrusted input or sanitize inputs. - Because the skill runs as a local script, run it under a non-privileged user account. If you need networked backup or cloud sync, prefer an explicit, well-reviewed mechanism rather than modifying the script without review. If you want, provide the remainder of the script (or the full repository) and I can re-check the portions that were truncated to raise confidence to high.
Capability Analysis
Type: OpenClaw Skill Name: budgetly Version: 2.0.1 BudgetLy is a local-only personal finance toolkit implemented as a Bash script. It manages financial records by appending timestamped entries to plain-text log files within the user's local data directory (~/.local/share/budgetly/). The script (scripts/script.sh) uses standard Unix utilities like grep, tail, and du, and contains no network calls, credential access, or suspicious execution patterns. The documentation (SKILL.md) accurately reflects the code's functionality without any prompt-injection risks.
Capability Assessment
Purpose & Capability
Name, description, SKILL.md, and the included Bash script all align: a local CLI for recording and exporting expense logs. There are no unexpected credentials, binaries, or services required.
Instruction Scope
Runtime instructions and the script operate only on files under a hardcoded data directory (~/.local/share/budgetly) and standard shell utilities. They do not reference external endpoints or unrelated system config. Note: data is stored in plain-text log files and the SKILL.md hardcodes the data path with no override.
Install Mechanism
No install spec; the skill is instruction-only with a single Bash script. No downloads, package installs, or archives are fetched by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. The script only uses HOME to build a per-user data directory (expected for a local CLI tool).
Persistence & Privilege
always is false and the skill does not request elevated or global agent privileges. It writes only to its own data directory and history log; it does not modify other skills or system-wide agent settings.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install budgetly
  3. After installation, invoke the skill by name or use /budgetly
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.0.1
update
v2.0.0
v2.5 standard: Use-when desc, homepage, source, security fix
v1.0.5
retry-fix-token
v1.0.4
old template -> domain-specific v2.0.0
v1.0.3
Quality upgrade
v1.0.2
Quality upgrade: custom functionality
v1.0.1
Quality fix: cleaner docs, removed flags
v1.0.0
Initial release
Metadata
Slug budgetly
Version 2.0.1
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 8
Frequently Asked Questions

What is Budgetly?

Set category budgets, log expenses, and visualize spending limits. Use when tracking grocery costs, monitoring subscriptions, or forecasting spend. It is an AI Agent Skill for Claude Code / OpenClaw, with 346 downloads so far.

How do I install Budgetly?

Run "/install budgetly" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Budgetly free?

Yes, Budgetly is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Budgetly support?

Budgetly is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Budgetly?

It is built and maintained by BytesAgain2 (@ckchzh); the current version is v2.0.1.

💬 Comments