How do I install the Cfo Validate skill?

Run npx skillmds@latest add mikechongcan/cfo-validate in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cfo Validate safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cfo Validate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cfo Validate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cfo Validate?

mikechongcan (@mikechongcan) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cfo Validate by mikechongcan — Agent Skill

Name: Cfo Validate
Author: mikechongcan

Cfo Validate

Run bean-check plus custom validation rules on the ledger. Ensures every entry balances, accounts exist, and no common errors are present. Use after any ledger modification to verify integrity. CLEAR step: L (Log)

mikechongcan d317b18 2.5 KB Updated Sep 17, 2026

File contents

/cfo-validate — Quality Control

CLEAR Step

L — Log: Ensure every entry in the ledger is valid and correct.

Role

You are the quality gate. Nothing gets committed without passing your checks.

Workflow

Step 1: Run validation helper

# Prefer explicit path when you know it
./bin/cfo-check ./ledger/main.beancount

# Or rely on auto-discovery
./bin/cfo-check

Discovery order:

The explicit path passed to ./bin/cfo-check
./main.beancount
./ledger/main.beancount
The first main.beancount found under the current working tree

Report any errors with file, line number, and description.

Step 2: Custom validation rules

Beyond bean-check, verify:

Balance assertions exist for every bank/credit card account at month-end
No orphaned accounts — every open account has at least one transaction
No future-dated transactions (unless explicitly flagged)
Consistent payee naming — flag variations (e.g., "Amazon" vs "AMZN" vs "Amazon.ca")
Receipt linkage — transactions over $75 should have a receipt reference
Tax treatment — all business expenses have tax metadata
Flagged transactions — report any ! (flagged) entries that need resolution
Duplicate-risk findings — surface unresolved items from the capture duplicate-risk report or manifest conflicts

Step 3: Report

VALIDATION REPORT
═══════════════════
bean-check:     PASS (0 errors)
Balance checks: PASS (12 assertions, all hold)
Orphan accounts: WARN (1 account with no transactions)
Future dates:   PASS
Payee names:    WARN (3 inconsistent names)
Receipts:       WARN (2 transactions >$75 missing receipts)
Tax treatment:  PASS
Flagged:        INFO (1 flagged transaction remaining)
Duplicate risk: WARN (1 corrected reimport waiting for approval)

Overall: PASS with warnings

Constraints

Run automatically before every /cfo-snapshot commit
Report all issues — never silently ignore
Distinguish ERROR (must fix) from WARNING (should fix) from INFO (awareness)

Related Skills

/cfo-capture-dedupe — emits duplicate-risk findings and import manifests
/cfo-snapshot — blocked until validation results are acceptable

---name: cfo-validatedescription: Run bean-check plus custom validation rules on the ledger. Ensures every entry balances, accounts exist, and no common errors are present. Use after any ledger modification to verify integrity. CLEAR step: L (Log)---# /cfo-validate — Quality Control## CLEAR Step**L — Log:** Ensure every entry in the ledger is valid and correct.## RoleYou are the quality gate. Nothing gets committed without passing your checks.## Workflow### Step 1: Run validation helper```bash# Prefer explicit path when you know it./bin/cfo-check ./ledger/main.beancount# Or rely on auto-discovery./bin/cfo-check```Discovery order:1. The explicit path passed to `./bin/cfo-check`2. `./main.beancount`3. `./ledger/main.beancount`4. The first `main.beancount` found under the current working treeReport any errors with file, line number, and description.### Step 2: Custom validation rulesBeyond bean-check, verify:1. **Balance assertions exist** for every bank/credit card account at month-end2. **No orphaned accounts** — every open account has at least one transaction3. **No future-dated transactions** (unless explicitly flagged)4. **Consistent payee naming** — flag variations (e.g., "Amazon" vs "AMZN" vs "Amazon.ca")5. **Receipt linkage** — transactions over $75 should have a receipt reference6. **Tax treatment** — all business expenses have tax metadata7. **Flagged transactions** — report any `!` (flagged) entries that need resolution8. **Duplicate-risk findings** — surface unresolved items from the capture duplicate-risk report or manifest conflicts### Step 3: Report```VALIDATION REPORT═══════════════════bean-check: PASS (0 errors)Balance checks: PASS (12 assertions, all hold)Orphan accounts: WARN (1 account with no transactions)Future dates: PASSPayee names: WARN (3 inconsistent names)Receipts: WARN (2 transactions >$75 missing receipts)Tax treatment: PASSFlagged: INFO (1 flagged transaction remaining)Duplicate risk: WARN (1 corrected reimport waiting for approval)Overall: PASS with warnings```## Constraints- Run automatically before every `/cfo-snapshot` commit- Report all issues — never silently ignore- Distinguish ERROR (must fix) from WARNING (should fix) from INFO (awareness)## Related Skills- `/cfo-capture-dedupe` — emits duplicate-risk findings and import manifests- `/cfo-snapshot` — blocked until validation results are acceptable

Frequently asked questions