skills/cap-table-explainer/SKILL.md
Explain a cap table, dilution, SAFEs, option pools, and round mechanics in plain English with the actual math. Use when asked to explain dilution, model a SAFE or priced round, size an option pool, understand a term sheet's economics, or figure out who owns what after a raise. Produces a worked ownership breakdown before/after the round, the dilution math step by step, and the traps founders miss. Not legal or financial advice.
npx skillsauth add mohitagw15856/pm-claude-skills cap-table-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.
Dilution math quietly decides how much of your company you keep. This skill walks through it with real numbers — pre/post-money, SAFEs, option pools, and conversions — so the founder sees exactly who owns what and why. Not legal or financial advice; confirm with counsel before signing.
Given partial terms, work the full example anyway with the numbers provided, and clearly state every assumption (e.g. assumed $1M pre-existing on a $X pre-money). If numbers are missing, pick clean illustrative ones and label them. Never leave the math as "[calculate]".
Ask for (if not already provided), else use labelled illustrative figures:
What this round does to ownership, in 3 sentences.
| Holder | Shares / % before | % after this round | |---|---|---| | Founders | | | | Existing investors | | | | Option pool | | | | New investor(s) | | | | Total | 100% | 100% |
The single dilution number that matters, and the one term quietly driving it.
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.