Analyze financial health using ratio categories: profitability, liquidity, leverage, efficiency, and valuation. Use this skill when the user needs to assess a company's financial performance, compare companies, evaluate creditworthiness, or prepare financial due diligence — even if they say 'is this company financially healthy', 'analyze these financial statements', or 'compare these two companies'.
npx skills add https://github.com/asgard-ai-platform/skills --skill biz-financial-ratios
Financial ratio analysis transforms raw financial statements into comparable metrics across five categories. Ratios are meaningful only in context — compare against industry benchmarks, historical trends, and peer companies.
Trigger conditions:
When NOT to use:
IRON LAW: Ratios Without Context Are Meaningless
A current ratio of 1.5 means nothing alone. Is 1.5 good? Compare to:
1. Industry average (retail ~1.2, manufacturing ~1.8)
2. Company's own trend (was it 2.0 last year? → declining liquidity)
3. Peers (competitor has 2.5? → relatively weak)
NEVER report a ratio without at least one comparison point.
IRON LAW: All Five Categories, Every Time
Analyzing only profitability misses a leveraged company about to default.
Analyzing only liquidity misses a profitable company's growth potential.
Cover all five categories for a complete picture.
1. Profitability — Is the company making money?
| Ratio | Formula | Measures |
|-------|---------|----------|
| Gross Margin | (Revenue - COGS) / Revenue | Production efficiency |
| Operating Margin | EBIT / Revenue | Core business profitability |
| Net Margin | Net Income / Revenue | Bottom-line profitability |
| ROE | Net Income / Equity | Return to shareholders |
| ROA | Net Income / Total Assets | Asset productivity |
2. Liquidity — Can it pay short-term obligations?
| Ratio | Formula | Healthy |
|-------|---------|---------|
| Current Ratio | Current Assets / Current Liabilities | > 1.5 |
| Quick Ratio | (Current Assets - Inventory) / Current Liabilities | > 1.0 |
| Cash Ratio | Cash / Current Liabilities | Context-dependent |
3. Leverage — How much debt is used?
| Ratio | Formula | Measures |
|-------|---------|----------|
| Debt-to-Equity | Total Liabilities / Equity | Capital structure |
| Interest Coverage | EBIT / Interest Expense | Ability to service debt |
| Debt-to-Assets | Total Liabilities / Total Assets | Asset financing |
> ⚠️ "Debt" definition: This skill (and the bundled script) defines "Debt" in the
> leverage ratios as Total Liabilities — not "long-term debt only" or "interest-bearing
> debt only". Both alternative definitions exist in textbooks and produce materially
> different ratios. If you need a different definition, document the choice explicitly
> and compute it manually; do not silently substitute.
4. Efficiency — How well are assets used?
| Ratio | Formula | Measures |
|-------|---------|----------|
| Inventory Turnover | COGS / Avg Inventory | Inventory management |
| Receivables Turnover | Revenue / Avg Receivables | Collection speed |
| Asset Turnover | Revenue / Total Assets | Asset productivity |
| Cash Conversion Cycle | DIO + DSO - DPO | Cash cycle speed |
5. Valuation — Is the stock fairly priced?
| Ratio | Formula | Measures |
|-------|---------|----------|
| P/E | Price / EPS | Price vs earnings |
| EV/EBITDA | Enterprise Value / EBITDA | Price vs cash generation |
| P/B | Price / Book Value per Share | Price vs net assets |
| Dividend Yield | Dividend per Share / Price | Income return |
> ⚠️ Decimal vs percent: The bundled script returns all profitability ratios
> (gross_margin, operating_margin, net_margin, roa, roe) as decimals —
> 0.35 means 35%, NOT 35.0. Liquidity and leverage ratios are already unitless
> multiples (e.g. current_ratio: 2.125). Render percentages only in the human-facing
> markdown report, never in JSON outputs.
# Financial Ratio Analysis: {Company}
## Summary Dashboard
| Category | Status | Key Metric |
|----------|--------|-----------|
| Profitability | 🟢/🟡/🔴 | {headline ratio} |
| Liquidity | 🟢/🟡/🔴 | {headline ratio} |
| Leverage | 🟢/🟡/🔴 | {headline ratio} |
| Efficiency | 🟢/🟡/🔴 | {headline ratio} |
| Valuation | 🟢/🟡/🔴 | {headline ratio} |
## Detailed Ratios
{Tables per category with ratio, value, industry avg, trend}
## Red Flags
- {specific concern with data}
## Overall Assessment
{Synthesized financial health verdict}
Scenario: Ratio analysis for a Taiwanese electronics manufacturer
| Ratio | Company | Industry | Trend | Flag |
|-------|---------|----------|-------|------|
| Gross Margin | 18% | 22% | ↓ from 21% | 🔴 Below peers, declining |
| Current Ratio | 1.8 | 1.5 | → stable | 🟢 Adequate |
| D/E | 1.2 | 0.8 | ↑ from 0.9 | 🟡 Rising leverage |
| Inventory Turnover | 4.2x | 6.0x | ↓ from 5.1x | 🔴 Slow inventory |
Synthesis: Profitability weakening + inventory building up + leverage rising = potential working capital crisis ahead ✓
| Script | Description | Usage |
|--------|-------------|-------|
| scripts/financial_ratios.py | Compute standard liquidity, leverage, profitability, and efficiency ratios | python scripts/financial_ratios.py --help |
Run python scripts/financial_ratios.py --verify to execute built-in sanity tests.
references/industry-benchmarks.mdAutomatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders. Turns hours of manual bookkeeping into minutes of automated organization.
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
This skill calculates key financial ratios and metrics from financial statement data for investment analysis
This skill provides an advanced financial modeling suite with DCF analysis, sensitivity testing, Monte Carlo simulations, and scenario planning for investment decisions
This skill retrieves upcoming earnings announcements for US stocks using the Financial Modeling Prep (FMP) API. Use this when the user requests earnings calendar data, wants to know which companies are reporting earnings in the upcoming week, or needs a weekly earnings review. The skill focuses on mid-cap and above companies (over $2B market cap) that have significant market impact, organizing the data by date and timing in a clean markdown table format. Supports multiple environments (CLI, Desktop, Web) with flexible API key management.
Crypto wallet operations via the awal CLI — sign in, check balances, send USDC/ETH/POL/SOL, trade tokens, fund the wallet, and use the x402 payment protocol to discover paid services, pay for API calls, monetize an API, or query onchain data. Use whenever the user mentions signing in, login, authentication, wallet status, balance, address, sending money, paying someone, transferring tokens, ENS names, swapping/trading/converting tokens, funding/topping up/onramp, USDC, ETH, POL, SOL, the x402 bazaar, paid APIs, monetizing an endpoint, or querying onchain data on Base.
Access real-time and historical stock market data, forex rates, cryptocurrency prices, commodities, economic indicators, and 50+ technical indicators via the Alpha Vantage API. Use when fetching stock prices (OHLCV), company fundamentals (income statement, balance sheet, cash flow), earnings, options data, market news/sentiment, insider transactions, GDP, CPI, treasury yields, gold/silver/oil prices, Bitcoin/crypto prices, forex exchange rates, or calculating technical indicators (SMA, EMA, MACD, RSI, Bollinger Bands). Requires a free API key from alphavantage.co.
Braintree Automation: manage payment processing via Stripe-compatible tools for customers, subscriptions, payment methods, and transactions
Take asgard-ai-platform/biz-financial-ratios from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.