financial-analysis
Skill0 starsChanged 4 months agoMITView on GitHub
Use when financial statements, ratios, or trends need to be analyzed — e.g. "analyze this company's financials", "what's the credit risk here", or "how has this metric trended". Provides a structured ratio/trend/red-flag workflow rather than an ad hoc read of the numbers.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- johnsonhk88/AI-Bank-Statement-Document-Automation-By-LLM-And-Personal-Finanical-Analysis-Predictiontheir own version, first seen Nov 8, 2026
- Celorus/celorus-plugintheir own version, first seen Nov 6, 2026
- Rswcf/deepviews-mcptheir own version, first seen Oct 20, 2026
- zeonium/Claude-Skillstheir own version, first seen Oct 15, 2026
- garri333/Skillstheir own version, first seen Oct 11, 2026
- hewi333/Mom-n-Pop-Skillstheir own version, first seen Jun 30, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- johnsonhk88/AI-Bank-Statement-Document-Automation-By-LLM-And-Personal-Finanical-Analysis-Prediction★ 631same name
- hewi333/Mom-n-Pop-Skills★ 121same name
- GAJETOso/financeskills★ 47same name
- abinauv/business-consulting★ 28same name
- HHFinAi/Institutional-Growth-Equity-Skills★ 3same name
- QYQSDTC/Financial_Analysis_Agent_Skill★ 2same name
- garri333/Skills★ 1same name
- lin30/claude-skills★ 1same name
- Rswcf/deepviews-mcp★ 1same name
- Celorus/celorus-plugin★ 0same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- agent-architecture-advisorSkill
- business-intelligenceSkill
- compliance-reviewSkill
- data-correlationSkill
- document-analysisSkill
- extractionSkill
- legal-contract-reviewSkill
- research-methodologySkill
- trace-analysisSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
1
Distinctive
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
- Distinctive: line 25
Every conclusion is based on a ratio or trend, not a single raw figure taken in isolation.
“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.
Files
Financial analysis
A structured workflow for reading financial statements: ratios in context, trends over single points, and a standing red-flag checklist — the discipline behind this repo's patterns/parallel credit-risk specialist, generalized into a reusable skill.
Workflow
- Establish the time series before judging any single number. One quarter's margin means little without at least 3-4 prior periods for comparison — request or gather history before concluding "good" or "bad."
- Compute ratios, don't eyeball raw figures. Debt-to-income, net margin, current ratio, cash-reserve-months — ratios normalize for scale and are what's actually comparable across time or between companies.
- Read trend direction, not just the latest value. A mediocre-but-improving metric and a strong-but-declining one need different conclusions even at the same absolute level.
- Run the red-flag checklist explicitly (see
references/red-flag-checklist.md) rather than relying on general impression — inconsistencies between related figures are the highest-signal red flags. - Contextualize against sector norms. A margin or leverage ratio that's alarming in one industry is normal in another — state the comparison basis, don't judge in a vacuum.
- Separate the finding from the recommendation. State what the numbers show first; make a lending/investment/risk recommendation as a distinct, clearly labeled step afterward.
Composition
Pairs with data-correlation when connecting financial trends to an external cause, and feeds business-intelligence when the analysis needs to become a decision recommendation.
Quality bar
- Every conclusion is based on a ratio or trend, not a single raw figure taken in isolation.
- The red-flag checklist was applied explicitly, not implicitly.
- Sector/context comparison basis is stated for any qualitative judgment ("high", "healthy", "concerning").
- Findings and recommendations are clearly separated.
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
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.