ericrisco/rsc-harness / skills/bookkeeping
bookkeeping
VerifiedUse when a small business needs audit-ready books — a chart of accounts, posting a transaction to the right account and side, clearing an uncategorized bank feed, cash vs accrual, or a ledger that won't tie to the bank. NOT interpreting the numbers — runway, burn, P&L cadence (that is `finance-ops`), NOT issuing invoices (that is `invoicing`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.8 KB |
| evals/README.md | markdown | 1.0 KB |
| evals/cases.yaml | config | 3.5 KB |
| references/chart-of-accounts.md | markdown | 3.4 KB |
| references/reconciliation-playbook.md | markdown | 3.7 KB |
| references/tricky-transactions.md | markdown | 9.0 KB |
evals/cases.yaml
View on GitHubskill: bookkeeping
should_trigger:
- prompt: "Set up a chart of accounts for my new consulting LLC."
why: Greenfield COA build — the foundation of the double-entry system, core to this skill.
- prompt: "I've got 300 bank transactions sitting uncategorized, help me sort them."
why: Bank-feed categorization to the right accounts; the Uncategorized=0 loop.
- prompt: "My books don't tie out to the bank statement this month."
why: Month-end reconciliation; non-obvious phrasing for "ledger ≠ bank balance."
- prompt: "Should I use cash or accrual accounting for my business?"
why: Accounting-method choice, with the gross-receipts ceiling and inventory trigger.
- prompt: "Which side is a debit when I pay rent?"
why: Core double-entry mechanics / normal-balance rules; non-obvious bookkeeping phrasing.
- prompt: "Categoriza estos movimientos del banco, mi contabilidad está hecha un desastre."
why: Spanish trigger — categorize the bank feed and clean up a messy ledger.
- prompt: "Where does a customer's upfront deposit post — is that revenue?"
why: Classification judgment; prepayment is a liability (unearned revenue), not revenue.
should_not_trigger:
- prompt: "Create and send an invoice to this client and chase the payment."
route_to: invoicing
why: Issuing accounts receivable and collecting, not recording an event in the ledger.
- prompt: "What should I charge for this consulting service?"
route_to: pricing
why: Price/margin setting, not classifying or balancing a transaction.
- prompt: "Build me a 3-year revenue and runway projection."
route_to: financial-model
why: Forward-looking forecasting, not recording what already happened.
- prompt: "What's our runway and burn rate right now?"
route_to: finance-ops
why: Interpreting the numbers for the business, not posting or reconciling them.
- prompt: "Pull our Stripe payouts via the API and sync them."
route_to: stripe
why: API integration work, not categorization or double-entry posting.
capability:
- scenario: >
Given six bank-feed lines for the month and no chart of accounts — (1) a $800 debit to
the landlord, (2) a $1,500 transfer to the owner's personal account, (3) a $2,000 wire
received from a customer for a project that has not started, (4) a $49 recurring charge
from a SaaS vendor, (5) a $600 payment to the bank against the business term loan,
(6) a $3,000 deposit for a consulting engagement completed this month —
produce a small chart of accounts and the correct journal entry for each, then state
the closing check that proves the books are done for the period.
must_include:
- Builds a small COA covering all five categories (asset, liability, equity, revenue, expense) with numbered ranges.
- Every journal entry has equal debits and credits, shown explicitly.
- Treats the owner draw as an equity account (Owner Draws), not an expense.
- Treats the loan principal repayment as a liability reduction (DR Loan Payable / CR Cash), not an expense.
- Treats the customer upfront payment as a liability (Unearned Revenue), not revenue.
- Posts rent and software as expenses (debit) against Cash (credit), and service revenue as a credit to Revenue against Cash (debit).
- States the closing discipline: the period is not done until the resulting ledger is reconciled against the bank statement (book balance must tie to bank balance, with any difference explained).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |