Financial report generator
Skill Komluc/agent-skills-production/skills/financial-report-generator
Production-grade agent skills for Claude Code, OpenAI Codex, Gemini CLI, and every platform implementing the Agent Skills open standard
npx -y skills add Komluc/agent-skills-production --skill financial-report-generatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generates a compliant financial report in IFRS, GAAP, or OHADA format. Use when the user requests a financial report, compliance document, accounting export, or any regulated financial output. Covers IFRS, GAAP, and OHADA standards. Do not use for informal financial summaries, exploratory analysis, or BI dashboards.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.1 KB, 580 tokens by cl100k_base, as published. Nobody here has run it
Step 1 — Identify the standard and jurisdiction
Ask the user:
- Accounting standard: IFRS / GAAP / OHADA
- Jurisdiction (for OHADA): which member state (TG, CI, SN, CM, GN, BJ, etc.)
- Report type: Income Statement / Balance Sheet / Cash Flow / Notes / Full set
- Period: fiscal year end date and comparative period
See references/standards-overview.md for jurisdiction → standard mapping.
If the user doesn't know their standard, use this heuristic:
- Listed company, international operations → IFRS
- US-based company → GAAP
- West/Central Africa entity → OHADA
Step 2 — Collect the financial data
Request from the user:
- Trial balance or chart of accounts export (CSV, XLSX, or paste)
- Any adjusting entries not yet booked
- Prior period comparative figures (if available)
If data is provided as a file, read it and verify:
- All accounts sum to zero (debit = credit)
- No missing account codes against the expected chart of accounts
- Currency is consistent
If validation fails, report all discrepancies before continuing.
Step 3 — Generate the report
Apply the appropriate template from references/:
| Standard | Template file |
|---|---|
| IFRS | references/ifrs-templates.md |
| GAAP | references/gaap-templates.md |
| OHADA | references/ohada-templates.md |
Rules for all standards:
- Round to the nearest whole currency unit (no cents in formal reports)
- All figures in thousands unless the entity is below the threshold
- Label the comparative column clearly
- Flag any material items (>5% of total assets or revenue)
Step 4 — Validation before output
Before presenting the report, verify:
- Balance sheet balances (Assets = Liabilities + Equity)
- Net income matches between Income Statement and Balance Sheet
- Cash flow ending balance matches Balance Sheet cash
- All required disclosures are present for the selected standard
If any check fails: report the discrepancy and do NOT output the report. Request corrected input data.
Step 5 — Output
Produce the report in this order:
- Cover page (entity name, period, standard, preparer)
- Financial statements (in standard order for the selected framework)
- Notes (mandatory disclosures only — no boilerplate)
Add this footer to every report:
Prepared using: financial-report-generator v1.2.0
Standard: [IFRS / GAAP / OHADA]
This document is a draft. Review by a qualified accountant is required
before filing or external distribution.