skills/financial-statement-explainer/SKILL.md
Explain a financial statement (P&L, balance sheet, or cash flow) in plain English. Use when asked to explain a P&L / income statement, a balance sheet, a cash flow statement, or to make financials understandable to a non-finance reader. Produces a plain-language walkthrough — what each section means, the line items that matter, the key ratios, and the story the numbers tell — so a non-accountant can read and act on it. Not financial advice.
npx skillsauth add mohitagw15856/pm-claude-skills financial-statement-explainerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Financial statements are precise but opaque to most people. This skill translates a P&L, balance sheet, or cash flow into plain English — what each part means, which numbers actually matter, and the story they tell about the business — so a founder, manager, or operator can read their own financials and make decisions.
Note: this is an educational explainer, not financial, investment, tax, or accounting advice. It explains figures the user provides; it does not audit them or recommend financial decisions. Verify numbers and any decisions with a qualified accountant/advisor. Never invent figures.
Given a statement (or a few key numbers), explain it anyway — walk through the structure and interpret the figures provided. Where a number isn't given, explain what to look for rather than inventing it. Never fabricate amounts or compute ratios from numbers you weren't given.
Ask for these only if they aren't already provided (else explain generally / mark unknown):
Financial-literacy practice — plain-language statement walkthroughs (P&L, balance sheet, cash flow), the ratios that matter, and the profit-vs-cash distinction.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.