Turn your monthly stack of statements, variance reports, bank statements and meeting minutes into a single, source-cited, board-ready briefing — in one command.
Every month, your property manager prepares a thorough package — balance sheets, variance reports, bank statements, manager's report, meeting minutes — covering the corporation's financial position in detail.
That detail is necessary, and it's a lot to integrate. Each document tells part of the story, and the most useful read of the corporation only emerges when you correlate across them: a variance line, a contractor quote in the manager's report, and a motion in last month's minutes can together describe a single emerging issue — separately, none of them does.
There's also a time dimension the current package can't show on its own. A board wants to see how the operating fund is tracking across the year, how reserve drawdown compares to the study's projection, and what was discussed in recent meetings that hasn't yet flowed into the statements.
I built this Claude Code skill to do that integration for me. I keep all my condo board materials in one directory, ask it to run the report, and get back a structured analysis with source citations, trend context across prior periods, priority flags, and a forward-looking section pulled from the minutes.
It saves a timestamped report each run and works incrementally — subsequent runs read only what's new and update only what changed.
Structured around the questions a board actually faces in the meeting room — with trend context, source citations, and forward-looking signals from the minutes.
Run it monthly, run it ad-hoc, or just ask focused questions — the structure stays consistent so you and your board can scan it the same way each time.
If you can run Claude Code, you can run this.
If you're here, you probably already have it. If not, install Claude Code and confirm you can run it from your terminal.
claude.ai/code ↗Claude Code picks up skills automatically — no further configuration needed.
One folder per corporation. Board meetings by month, semi-permanent documents alongside. The skill creates Reports/ on the first run.
See the layout ↓Open Claude Code in your corporation's directory and ask:
Run the financial report. · How is the reserve fund tracking against the study projections? · Show me the arrears trend.
— the only commands you really need to learnThis is the layout the skill was developed against. Other structures may work — this one is the path of least resistance.
The skill reads documents the way you'd flip through them — by what's in the filename and what's on the page. There's no schema to maintain, and the naming convention is whatever you'd already use to keep the materials organized.
Subsequent runs read only what's new and update only what changed, so incremental cost stays low and the report stays consistent month over month.
An Ontario reference file is included. For other jurisdictions the skill prompts you with instructions to generate one — so the reserve-fund context, statutory categories, and reporting conventions stay accurate to where the corporation actually operates.
Every variance, flag, and number traces back to a specific file and page or section. The board can verify before adopting. Trust, but verify — especially when an AI did the synthesis.
The skill detects which files are new and re-uses what hasn't changed. The first run does the heavy lift; every run after just updates what's moved. The Reports directory keeps a timestamped trail.
The output is structured around what a board actually has to decide on: priority flags, forward-looking commitments, and a scorecard at the front. It complements the formal financial package rather than reproducing it.
It's developed and tested in Claude Code. The skill format may be portable to other coding agents — untested, but the structure is plain Markdown and reference files, not Claude-specific glue.
The repo is public under AGPL-3.0. Fork it, extend it, contribute the jurisdiction reference for your province or state. Pull requests welcome.
This project is a personal tool shared for informational purposes only. It is not professional financial, legal, or accounting advice, and should not be treated as such under any circumstances.
The author makes no representations or warranties of any kind — express or implied — regarding the accuracy, completeness, reliability, or fitness for any purpose of any output produced by this skill. AI models make mistakes. Reports generated by this skill may contain errors, omissions, or misinterpretations. Verify everything against your source documents before acting on anything.
By using this tool you agree that the author bears no responsibility whatsoever for any consequences arising from its use — including financial, governance, legal, privacy, or any other outcome. Use entirely at your own risk.
Clone the repo, point it at your board folder, ask it to run the report. That's the whole loop.