Agent skill

Financial Statement Analysis

by cbrock84 in cbrock84/headcount

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…

MITAuto-check passedBusiness, Finance & HR

Install Financial Statement Analysis

skills CLI
$ npx skills add cbrock84/headcount --skill financial-statement-analysis -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cbrock84/headcount financial-statement-analysis --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/finance/skills/financial-statement-analysis .claude/skills/financial-statement-analysis && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
financial-statement-analysis
GitHub stars
2k
Token cost
~1.3k tokens
SKILL.md length
681 words
Files
2 (incl. references)
Skills in repo
175
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Tasks that involve Financial analysis
  • SKILL.md covers Read the three statements…, Do fluctuation analysis before…, Compute ratios against the… and Benchmark within industry and…, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Financial Statement Analysis is an agent skill from cbrock84/headcount. 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.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

It sits in Business, Finance & HR, covering Financial analysis. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

When your agent uses it

  • Tasks that involve Financial analysis

Example prompts

  • “s or target”
  • “Use the financial-statement-analysis skill to read a set of financial statements and establishes what changed and why — fluctuation analysis against…”
  • “/financial-statement-analysis”

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Financial Statement Analysis loads about 1.3k tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 124 tokens; SKILL.md has 681 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~124
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 681 words, ~1,266 tokens.

Download SKILL.mdSave it as .claude/skills/financial-statement-analysis/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
financial-statement-analysis
description
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.

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.

Show full SKILL.md (272 more words)Show less

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.

© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/finance/skills/financial-statement-analysis of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Financial Statement Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Financial Statement Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Financial Statement Analysis this skillcbrock84/headcount2k—~1.3kAutomated safety check: PassMIT
Financial Analyzinghuangjia2019/claude-code-engineering1.1k1 repos~474Automated safety check: PassNone
Longbridge Earningshelsome/folio2691 repos~2.5kAutomated safety check: PassNone
Fundamentalsstaskh/trading_skills3741 repos~836Automated safety check: PassMIT
Earnings AnalysisWind-Alice/AliceMarket1303 repos~2.2kAutomated safety check: PassNone
Buy Side Equity Research Memohaskaomni/serenity-skill632—~3.8kAutomated safety check: PassMIT

Similar skills

  • Financial Analyzing

    huangjia2019/claude-code-engineering

    Analyze financial data, calculate financial ratios, and generate analysis reports.

    1.1k GitHub starsUsed in 1 repo~474 tokens
    Business, Finance & HRAuto-check passed
  • Longbridge Earnings

    helsome/folio

    Earnings analysis — pre- and post-earnings. An agent skill from helsome/folio.

    269 GitHub starsUsed in 1 repo~2.5k tokens
    Business, Finance & HRAuto-check passed
  • Fundamentals

    staskh/trading_skills

    Get fundamental financial data including financials, earnings, and key metrics.

    374 GitHub starsUsed in 1 repo~836 tokens
    Business, Finance & HRAuto-check passed
  • Earnings Analysis

    Wind-Alice/AliceMarket

    Create professional equity research earnings update reports (8-12 pages, 3,000-5,000 words) analyzing quarterly results for companies already under coverage.

    130 GitHub starsUsed in 3 repos~2.2k tokens
    Business, Finance & HRAuto-check passed
  • Buy Side Equity Research Memo

    haskaomni/serenity-skill

    Generate source-backed buy-side equity research memos from a ticker, starting with investment view, target-price scenarios, SEC and IR-backed financial statement analysis, industry chain…

    632 GitHub stars~3.8k tokensUpdated 2 mo ago
    Business, Finance & HRAuto-check passed
  • ERPClaw ERP Controller

    avansaber/erpclaw

    Operates the ERPClaw self-hosted ERP in plain language: accounting, invoicing, inventory, purchasing, tax, HR, payroll and reports, treating the ERP as the single source of truth.

    114 GitHub stars~15k tokensUpdated 2 days ago
    Business, Finance & HRAuto-check passed

More from cbrock84/headcount

All 175 skills in this repo
  • Agent Hierarchy

    cbrock84/headcount

    Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…

    2k GitHub stars~1.2k tokensUpdated 20 days ago
    Auto-check passed
  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 20 days ago
    Auto-check passed
  • Account Based Marketing

    cbrock84/headcount

    Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…

    2k GitHub stars~1.2k tokensUpdated 20 days ago
    Auto-check passed
  • Activation

    cbrock84/headcount

    Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.

    2k GitHub stars~865 tokensUpdated 20 days ago
    Auto-check passed
  • AI Research Analyst

    cbrock84/headcount

    Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.

    2k GitHub stars~916 tokensUpdated 20 days ago
    Auto-check passed
  • AI Search Optimization

    cbrock84/headcount

    Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf.

    2k GitHub stars~829 tokensUpdated 20 days ago
    Auto-check passed

Questions about Financial Statement Analysis

What does Financial Statement Analysis 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…. Financial Statement Analysis is an agent skill from cbrock84/headcount. 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.

When should I use Financial Statement Analysis?

Financial Statement Analysis fits situations like: tasks that involve Financial analysis.

How do I install Financial Statement Analysis in Claude Code?

Run `npx skills add cbrock84/headcount --skill financial-statement-analysis -a claude-code`. Or copy the skill folder (plugins/finance/skills/financial-statement-analysis in cbrock84/headcount) into .claude/skills/financial-statement-analysis in your project. Claude Code loads it when a task matches its description.

How do I install Financial Statement Analysis in Codex?

Run `npx skills add cbrock84/headcount --skill financial-statement-analysis -a codex`. Or copy the skill folder (plugins/finance/skills/financial-statement-analysis in cbrock84/headcount) into .agents/skills/financial-statement-analysis in your project. Codex loads it when a task matches its description.

Can I use Financial Statement Analysis in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill financial-statement-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/financial-statement-analysis, .gemini/skills/financial-statement-analysis, .github/skills/financial-statement-analysis and .opencode/skills/financial-statement-analysis in your project.

What does Financial Statement Analysis need to run?

SKILL.md names no scripts, command-line tools or credentials: Financial Statement Analysis is instructions for the agent only.

Does Financial Statement Analysis access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Financial Statement Analysis safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Financial Statement Analysis use?

Financial Statement Analysis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Financial Statement Analysis use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 252 tokens, read only when the agent opens those files.

What are the alternatives to Financial Statement Analysis?

Skills that share tags, products or a category with Financial Statement Analysis: Financial Analyzing (huangjia2019/claude-code-engineering, 1.1k stars), Longbridge Earnings (helsome/folio, 269 stars), Fundamentals (staskh/trading_skills, 374 stars) and Earnings Analysis (Wind-Alice/AliceMarket, 130 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Financial Statement Analysis?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,007 GitHub stars. The repository holds 175 skills in this directory. The repository was last updated on September 17, 2026.

Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.