phoenixclaw-ledger

**Quick judgment** A strong, well-scoped plugin for **personal, passive expense tracking** inside PhoenixClaw. It’s best suited for users who already rely on PhoenixClaw for journaling and want automatic, “zero-effort” logging of day-to-day spending and simple budgeting—not for professional accounting, tax reporting, or precise business bookkeeping. **What it does well** - **Passive data capture**: Watches PhoenixClaw “moments” and payment screenshots to infer transactions without manual entry. - **Good coverage of basic finance needs**: semantic expense detection, screenshot OCR, automatic categorization, monthly budget, savings goals, and trend/summary reports (daily/weekly/monthly/yearly). - **Tight ecosystem integration**: Uses PhoenixClaw’s cron, file layout, and post-analysis hooks to keep a consistent ledger (`ledger.yaml`, `budget.yaml`, `goals.yaml`, reports in Journal folders). - **Natural-language interaction**: Supports queries like “How much did I spend this month?” or “Set my monthly budget to X,” making it more accessible than raw spreadsheets. **Key risks and limitations** - **Data accuracy & completeness**: - Semantic detection and OCR can miss or mis-parse transactions (e.g., ambiguous chat mentions, low-quality screenshots, unusual payment formats). - Deduplication helps but cannot guarantee that every transaction is captured exactly once; manual spot-checking is advisable for important budgeting decisions. - **Privacy & security**: - Concentrates sensitive financial information in PhoenixClaw’s local data directory; risk depends on how securely the host system and PhoenixClaw environment are managed. - Not designed for shared or multi-user contexts where cross-access to finances would be problematic. - **Not accounting-grade**: - No evidence of double-entry accounting, reconciliation with bank feeds, or compliance features. - Unsuitable as the sole system of record for businesses, taxes, or regulatory reporting. - **Ecosystem dependency**: - Relies on PhoenixClaw Core’s cron and file structure; users must be comfortable with that tooling and configuration. **Recommended scenarios** Use this skill if you: - Already use PhoenixClaw daily and want **automatic personal expense logging** and **lightweight budgeting**. - Frequently mention money or share payment screenshots in your captured moments and are okay with approximate but convenient tracking. - Want **weekly/monthly spending insights** and simple financial goals embedded in your existing journal workflow. Avoid relying on it as your primary system if you: - Need **audit-grade accuracy**, business accounting, or tax-ready reporting. - Are highly sensitive about financial data and don’t want that information stored and processed within your PhoenixClaw environment.