agentleFS
Sign inStart free
gutierrezwgutierrezw/claude-skills/analyzing-financial-statements/SKILL.md

analyzing-financial-statements

Skill1 starsChanged 5 months agoNo licenceView on GitHub

Calculate, interpret, and benchmark financial ratios from income statements, balance sheets, and cash flow data. Use this skill whenever the user mentions financial ratios, fundamental analysis, company valuation, stock screening, or wants to evaluate a company's financial health. Triggers on: "calculate ratios", "analyze financials", "P/E ratio", "ROE", "ROA", "debt to equity", "liquidity analysis", "analyze balance sheet", "valuation metrics", "is this stock undervalued", "compare to industry benchmarks", "financial health check", "fundamentals of [company]", "gross margin", "operating margin", "EPS", "EV/EBITDA", or any request involving financial statement data — even if the user doesn't explicitly say "ratios". Also use when the user pastes raw financial figures and asks what they mean or whether a company looks attractive.

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use mcp-builder and skill-creator.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    mcp-builder

    Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 1 is common, 6 are distinctive, and 1 is very specific to this project.

  • 1

    Common

    Most of the 8 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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