cfo-briefing
Skill4 starsChanged 7 months agoMITView on GitHub
Use when preparing a concise CFO-ready operating brief from finance data, KPIs, risks, cash, revenue, AR, forecast, and close-status inputs.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- krishagel/geoffreytheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- krishagel/geoffrey★ 9same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- ar-collectionsSkill
- contract-to-invoiceSkill
- dunning-emailsSkill
- finance-close-checklistSkill
- invoice-health-checkSkill
- payment-reconciliationSkill
- revenue-recognition-qaSkill
- usage-billing-reviewSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to turn messy finance inputs into an executive-ready operating brief.
- Distinctive: line 21
Call out what changed since the prior period and why it matters.
- Distinctive: line 22
Keep the brief short enough for an executive to scan before a meeting.
- Distinctive: line 36
Do not overstate precision when inputs are preliminary.
- Distinctive: line 37
Do not bury cash, runway, covenant, or collection risks.
- Distinctive: line 38
Do not invent causal explanations.
- Distinctive: line 39
Keep customer-sensitive and employee-sensitive details out of general executive summaries unless needed.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CFO Briefing
Use this skill to turn messy finance inputs into an executive-ready operating brief.
Inputs
- KPI exports, financial statements, forecast, pipeline, cash position, AR/AP aging, close status, and board or investor questions.
- Prior-period comparisons, budget, forecast, and materiality threshold.
- Known risks, decisions needed, and audience.
Workflow
- Identify the briefing audience and time horizon: weekly operator update, board prep, investor update, lender update, or internal leadership meeting.
- Extract the most decision-relevant changes in cash, revenue, margin, burn, runway, collections, bookings, churn, forecast, and close status.
- Separate facts, interpretations, risks, and asks.
- Call out what changed since the prior period and why it matters.
- Keep the brief short enough for an executive to scan before a meeting.
Output
Return:
- Headline: one sentence on the state of the business.
- Metrics table with current value, prior value, plan/forecast, variance, and note.
- Key risks and mitigations.
- Decisions needed.
- Appendix items or data gaps.
Guardrails
- Do not overstate precision when inputs are preliminary.
- Do not bury cash, runway, covenant, or collection risks.
- Do not invent causal explanations. Mark them as hypotheses if not proven.
- Keep customer-sensitive and employee-sensitive details out of general executive summaries unless needed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

