Skill UI

This skill provides comprehensive methodologies for calculating Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM). It guides users through top-down, bottom-up, and value theory approaches for startup strategy, fundraising, and business planning. Ideal for validating market opportunities and defining realistic growth projections.

This skill acts as a specialized security expert for analyzing project dependencies. It scans dependencies across multiple ecosystems (e.g., npm, pip, Maven) to identify known vulnerabilities, assess associated risks, and generate Software Bill of Materials (SBOMs). It provides comprehensive insights into supply chain security and offers automated strategies for remediation, ensuring compliance and stability during development.

This skill creates comprehensive 3-5 year financial models for startups, including revenue projections, cost structures, and cash flow analysis. It covers headcount planning, unit economics like CAC and LTV, and three-scenario modeling (conservative, base, optimistic) to support fundraising and strategic planning.

Create comprehensive 3-5 year financial models for early-stage startups, including revenue projections, cost structures, cash flow analysis, and scenario planning. Supports fundraising, operational strategy, and investor presentations with cohort-based revenue modeling and headcount planning.

Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit/integration/contract/E2E/smoke classification, bug-to-test regression protection, consumer/provider contract testing, test-necessity review, and pre-delivery evidence review.

This skill performs a full-sweep analysis across code decay, architecture, tech debt, and test quality. It applies fixes directly to the codebase with safety checks. Safe changes are auto-applied, while risky changes require confirmation. Based on twelve classic engineering books, it triggers when users want to fix everything or clean up the whole project in a single command.