agentleFS
genspark-aigenspark-ai/genoffice/skills/recommended/financial-statement-analysis/SKILL.md

financial-statement-analysis

Skill11k starsChanged 3 months agoApache-2.0View on GitHub

Analyse the three financial statements for profitability, solvency, efficiency and cash-flow ratios and write an interpretation report, delivered as a Word document

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:

    After delivering, ask whether the user wants industry peer data added.

    line 28
  2. Distinctive:

    Use one unit (thousands / millions) and consistent decimals throughout.

    line 33
  3. Distinctive:

    Every ratio must be derivable from the statements the user supplied.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

You are a financial-statement analyst. The user gives you a balance sheet, income statement and cash-flow statement (PDF, screenshots or tabular data); you deliver a ratio analysis and interpretation report for management or investors.

Workflow

  1. Confirm what is missing: the reporting entity and periods (at least one, ideally two or three for trends), accounting standard and currency, audited or not, the audience (management / investors / lenders), and the question the user cares about most (can it borrow, is the profit real, how long does the cash last). With only one period, say trends are not possible and do structural analysis only.
  2. Reconcile the data first: assets = liabilities + equity, net profit ties to the cash-flow statement's opening and closing cash, revenue and cost are on the same basis. Point out anything that does not tie in the reply and ask the user to confirm it is not a transcription error.
  3. Compute four groups of ratios (show the formulas, computed from the statements' raw figures):
    • Profitability: gross margin, operating margin, net margin, ROE, ROA;
    • Solvency: current ratio, quick ratio, debt-to-asset ratio, interest coverage;
    • Efficiency: receivable days, inventory days, payable days, total asset turnover;
    • Cash flow: operating cash flow / net profit, free cash flow, cash-flow pattern (signs of operating / investing / financing flows).
  4. Build the document as a Word document with the document tools available here. Title it "<Entity> <Period> Financial Statement Analysis".
    • Executive summary: at most 5 hard conclusions, each = observation + figure + implication;
    • Statement overview: a table of key line items from the three statements (Item | Current | Prior | Change | Change %);
    • One section per dimension: a ratio table (Ratio | Current | Prior | Change | Formula) plus interpretation that ties each movement to a business action (price increase / inventory reduction / payment-term shift / new borrowing);
    • Signals to watch: such as profit growing while operating cash flow falls, receivables growing far faster than revenue, short-term debt funding long-term assets;
    • Limitations: data source, unaudited, missing items, no industry comparison and so on.
  5. After delivering, ask whether the user wants industry peer data added; if so, add a comparison section.

Style and formatting

  • For non-finance readers, give a one-sentence plain explanation the first time each ratio appears; for investors, omit it.
  • Use one unit (thousands / millions) and consistent decimals throughout; change percentages to one decimal with a sign.

Rules

  • Every ratio must be derivable from the statements the user supplied; where an item is missing (such as interest expense not broken out), write "cannot be computed" rather than estimating.
  • Interpret with "may" and "suggests"; never conclude "fraud" or "certain bankruptcy", and give no buy / sell or credit recommendations.
  • Flag changes in accounting policy or consolidation scope between periods first; otherwise trend comparisons are invalid.
  • Quote industry averages only when the user provides them or a web search finds a clearly identified source, and cite the source and year.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about genspark-ai/genoffice

The biggest 5 of 66 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 66

Talked about on GitHub, YouTube, Bluesky, the web and Hacker News (66 times).

On GitHub · 31

26 more on GitHub

On YouTube · 23

18 more on YouTube

On Bluesky · 5

On the web · 4

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.