Financial Statement Analysis logo

Financial Statement Analysis

CommunityPopular
cbrock84
financial-statement-analysis

Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or target's financials, diagnose a deteriorating trend, explain a variance to someone who will act on it, or test whether an adjusted number is honest.

Overview

Publishercbrock84
Repositoryheadcount
Skill namefinancial-statement-analysis
Stars
1.6K
Forks
237
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by cbrock84 on GitHub. Read the source before you install it.

Installation

Install the Financial Statement Analysis AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/cbrock84/headcount.git /tmp/headcount
mkdir -p .claude/skills
cp -r /tmp/headcount/plugins/finance/skills/financial-statement-analysis .claude/skills/financial-statement-analysis
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Financial Statement Analysis in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Financial Statement Analysis on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Financial Statement Analysis is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Financial statement analysis

The statements tell you what happened. Analysis tells you why, and whether it continues.

Read the three statements against each other

A single statement is almost never enough. The income statement reports profit, the cash flow statement reports cash, and the gap between them is usually the story.

  • Net income rising while operating cash flow falls is the signal worth chasing first. It means working capital is absorbing the growth, or revenue is being recognized ahead of collection.
  • The balance sheet is a point in time; the other two cover a period. Comparing a period figure to a point-in-time balance without averaging the balance overstates efficiency ratios.
  • Read the notes. Concentration of customers, debt maturities, commitments, related parties, and subsequent events routinely matter more than anything on the face of the statements.

Do fluctuation analysis before you compute a single ratio

Compare against the prior period and against budget. They answer different questions: prior period tells you what changed, budget tells you whether you understood your own business.

  • Set a threshold in both currency and percent. Percent alone sends you chasing large swings on small accounts; currency alone hides a small account that doubled.
  • Explain with a driver, not a restatement. "Revenue up 12%" is the observation, not the explanation. Volume, price, mix, timing, and one-off items are explanations.
  • Track how many variances you cannot explain. A close where three material movements have no owner is telling you something about the underlying records, not about performance.

Compute ratios against the question you actually have

  • Profitability — gross margin, operating margin, net margin, return on invested capital.
  • Liquidity — current and quick ratio, and the one that usually matters more in practice, days of cash on hand.
  • Leverage and solvency — debt to EBITDA, interest coverage, debt to equity.
  • Efficiency — days sales outstanding, days payable outstanding, days inventory outstanding, and the cash conversion cycle they combine into.

Ratios are comparative instruments. One ratio at one date means close to nothing; the trend across periods and the comparison to peers are where the information is.

Benchmark within industry and roughly within scale

Gross margin compared across industries is noise. So is comparing a company at $5M to one at $500M on cost structure — the second has fixed costs the first cannot carry and buying power the first cannot access.

Internal benchmarking across segments, regions, or product lines is often more useful than external comparison, because the accounting policies are already consistent.

Test non-GAAP measures before you repeat them

EBITDA, adjusted EBITDA, free cash flow, core earnings, adjusted net income, annual recurring revenue. These exist for a real reason — statutory profit includes items that obscure operating performance — and also because management chooses the adjustments.

  • Ask what was added back, and whether it recurs. A restructuring charge that appears every year is an operating expense wearing a different label.
  • Ask whether the adjustment would survive good results. Adjustments that only appear in bad quarters are presentation, not measurement.
  • Reconcile to the nearest statutory measure and show the reconciliation. A number that cannot be tied back is not a measure, it is an assertion.

Diagnosing a deteriorating trend

Work from the top down and stop at the first level that explains it. Revenue, then gross margin, then operating expense, then working capital, then financing cost. Most deterioration that looks like a demand problem is a margin or working capital problem, and the two call for different responses.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Present a ratio with no trend and no comparison. A number standing alone is decoration.
  • Explain a variance by restating it in different words.
  • Repeat an adjusted measure without seeing what was added back.
  • Annualize a partial period without saying you did, or apply a seasonal quarter as a run rate.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Financial Statement Analysis AI skill do?

Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or target's financials, diagnose a deteriorating trend, explain a variance to someone who will act on it, or test whether an adjusted number is honest.

Why use Financial Statement Analysis on TypingMind?

Because you install it once and use it with any model. Financial Statement Analysis is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Financial Statement Analysis in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cbrock84/headcount/tree/main/plugins/finance/skills/financial-statement-analysis. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Financial Statement Analysis?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Financial Statement Analysis?

As many as you like. As long as a model supports skills, you can use Financial Statement Analysis with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Financial Statement Analysis AI skill free?

Yes. It is published on GitHub by cbrock84 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇