agentleFS
Sign inStart free
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/financial-statement-diagnostic/SKILL.md

financial-statement-diagnostic

Skill1 starsChanged 24 days agoMITView on GitHub

Diagnoses financial health across linked statements when performance, solvency or accounting signals need structured interpretation.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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
  1. Distinctive:

    Use for periodic health checks, unexpected result changes or preparation for important financing decisions.

    line 9
  2. Distinctive:

    Run horizontal and common-size analysis across all three statements.

    line 19
  3. Distinctive:

    Every conclusion points to a figure or stated assumption.

    line 31

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Financial Statement Diagnostic

When to use it

Use for periodic health checks, unexpected result changes or preparation for important financing decisions.

What Claude needs

  • Background from client-context.md
  • Income statements, balance sheets and cash flow statements
  • Prior periods, budget and available management adjustments
  • Accounting policies and unusual transaction notes

Method

  1. Standardise periods and map accounts into consistent operating categories.
  2. Run horizontal and common-size analysis across all three statements.
  3. Trace profit to operating cash through working capital and non-cash items.
  4. Calculate liquidity, leverage, coverage, efficiency and margin indicators.
  5. Separate recurring performance from timing effects and exceptional items.
  6. Build an issue tree linking symptoms, likely causes and evidence needed.

Output format

Provide an executive diagnosis, indicator table, statement bridges and prioritised issue tree. Label each finding as fact, inference or open question.

Quality checks

  • The balance sheet balances and statement links reconcile.
  • Like-for-like periods and definitions are used.
  • Every conclusion points to a figure or stated assumption.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free