PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mohitagw15856/pm-claude-skills --skill financial-statement-explainergit clone --depth 1 https://github.com/mohitagw15856/pm-claude-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/financial-statement-explainer)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/financial-statement-explainer"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/financial-statement-explainer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/financial-statement-explainer"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/financial-statement-explainer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00107 | $0.00983 |
| Opus 5.5 | $0.00043 | $0.00393 |
| Sonnet 5.5 | $0.00021 | $0.00197 |
| Haiku 4.5 | $0.00011 | $0.00098 |
Grade A, and why
financial-statement-explainer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Financial Statement Explainer Skill
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.
Working from a brief
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.
Required Inputs
Ask for these only if they aren't already provided (else explain generally / mark unknown):
- The statement — which one (P&L / balance sheet / cash flow), the figures, and the period.
- The reader — who needs to understand it and why (a founder, a manager, an investor conversation).
- The question behind it — what they're trying to learn (Are we profitable? Can we make payroll? Why is cash tight?).
- Context — business type/stage, if it helps interpret what's normal.
Output Format
[Statement] Explained
- What this statement tells you — one or two lines on what this statement is for (P&L = profitability over a period; balance sheet = what you own/owe at a point; cash flow = where cash actually moved).
- Section-by-section — walk the structure in plain terms, using the provided numbers:
- P&L: revenue → COGS → gross profit/margin → operating expenses → operating income → net income; what each step means.
- Balance sheet: assets, liabilities, equity; the accounting equation; what current vs. long-term means.
- Cash flow: operating, investing, financing; why profit ≠ cash.
- The numbers that matter — the few line items and ratios worth watching for this reader (e.g. gross margin, burn, current ratio, runway) — with the formula and the figure if the inputs were given.
- The story — what the statement is saying overall (healthy/strained, improving/declining, where to look).
- Watch-outs & next questions — what looks notable and what to ask an accountant.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 71 lines · 107 tokens per session scan A ff6187833c4e
financial-statement-explainer is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 107 tokens to every session and 983 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-12.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…