Claude Skills by masterleopold

Capture book pages from Mac Kindle, Apple Books, Kindle Cloud Reader, or PDF files, then OCR and generate structured Obsidian Markdown. Activates when user mentions capturing a book, Kindle screenshots, Apple Books capture, book OCR, book-to-markdown conversion, or extracting text from book page images.

Auto-generate 5 sales support materials for pipeline Steps 5-7 — competitive comparison table, 3-year TCO analysis, internal proposal template, objection rebuttals, phased implementation timeline. Core principle is arming the buyer to sell internally. Use when deals reach Step 5+ or when win rates at Steps 5-7 are low.

Nudge-based choice architecture for 3-option selection UI — smart default vs active choice, outcome mapping, channel factors, RECAP, operational transparency with source attribution, post-decision reinforcement, error-forgiving undo, peak-end session design, user contribution acknowledgment. Use when presenting options to founders, designing choice flows, or optimizing decision quality.

Contextual confidence calibration — DEFLATE for One-Way Doors and RED zones, PROTECT for Two-Way Doors and fundraising, "How does this work step by step?" depth testing, values-to-consequences redirect, unanimity as risk signal. From Knowledge Illusion — overconfidence is sometimes functional. Use when calibrating response intensity, testing founder assumptions, or navigating motivational vs analytical contexts.

Content generation rules — customer-as-protagonist rewriting, inflated language filter, precision targeting, sell results not products, and anticipatory selling material generation for sales Steps 5-7. Use when generating any content, reviewing drafts, or creating sales support materials.

Theory of Constraints 5 Focusing Steps, buffer management with 3-zone traffic light, relay runner execution discipline, WIP limits, and late start scheduling. Use when managing Goal execution pace, detecting bottlenecks, or when buffer status changes.

Erin Meyer's Culture Map with 8 dimensions, 5 launch presets (US, JP, DE, UK, FR), Layer A agent-user adaptation, Layer B content-target market adaptation, and anti-sycophancy tone calibration per culture. Use when adapting communication style to the founder's culture, localizing content for target markets, or when cultural friction appears in interactions.

Disruption analysis using Innovator's Dilemma economics, cannibalization exposure, competitor response classification, market entry signals, and six-force environmental monitoring. Use when evaluating competitive landscape, entering markets with incumbents, or during periodic strategic scans.

Sarasvathy's effectuation framework for pre-PMF exploration, post-pivot situations, and Knightian uncertainty. Use when goals are unclear, markets are illegible, or historical data is absent. Replaces standard causation planning.

4 strategic failure patterns from Essence of Failure — dual-objective trap (conflict stress test), strategic ambiguity (operationalizability test), withdrawal decision protocol (pre-committed stop conditions, re-present biweekly), assumption provenance auditing (source, verification, load-bearing flag, sample size). Use when creating strategy, detecting organizational dysfunction, or when decisions seem stuck.

YC weekly growth benchmarks, T2D3 SaaS trajectory, compound projection formula, growth rate auto-calculation, North Star metric enforcement by business model, vanity metric detection, and metric definition lock. Use when tracking growth, setting targets, evaluating progress, or when the founder proposes a metric that may be misleading.

KPI tree decomposition from Goal to Drivers, formula-based factorization, impact_weight assignment and dynamic update, Crux identification via importance x tractability, constraint Driver identification, input vs output metric classification. Use when decomposing Goals, prioritizing Drivers, or re-evaluating impact weights.

Andrew Chen's Cold Start Problem framework — atomic network definition with thresholds by product type, anti-peanut-buttering, zero tracking, escape velocity 3-force decomposition (engagement/acquisition/economic), growth ceiling 5-force detection, competitive position dynamics, T2D3 benchmark. Use for products with network effects, marketplace dynamics, or viral growth potential.

Cash Machine 10-step B2B sales pipeline with 3 presets, verifiable checkpoints per step, trajectory logging, bottleneck detection with utilization formula, lead qualification gate (BANT 6-criteria), pipeline velocity and stall detection (2x threshold), two-tier probability scoring, BBS tracking, end-of-quarter syndrome detection. Use when managing sales pipeline, detecting bottlenecks, or forecasting revenue.

Plan B framework — 6 environmental forces monitoring, pre-mortem 5-step process, scenario planning with auto-trigger points, Devil's Advocate on every proposal, 100-day gate reviews, S-curve awareness, 5 hurdles to Plan B execution, boomerang prevention. Use when preparing contingencies, monitoring environmental changes, or when the current plan shows signs of failure.

Pre-mortem analysis, scenario planning, future state narratives, and contingency frameworks. Use before finalizing any Strategy Kernel, when planning major initiatives, or when preparing Plan B triggers.

Lead qualification using BANT 6-criteria gate (Problem, Budget, Authority, Timeline, Fit, Margin) at marketing-sales handoff. Qualified leads enter pipeline, unqualified go to nurture. If bottleneck is downstream, reduce upstream lead gen. Use when evaluating leads, managing marketing-sales handoff, or when pipeline quality is poor.

QUEST Socratic interview methodology — beginner stance, empathic neutrality, downward/upward questioning, echo questions, concept identification, permission checks, critical point pursuit, anti-pattern safeguards, resolution imbalance diagnostic, workaround discovery, painkiller vs vitamin test, locally famous test. Use during onboarding, when gathering business context, or during post-choice conversational follow-up.

Cohort retention analysis — triangle chart construction, curve shape analysis for PMF detection (flattening/declining/rising), layer cake chart, PMF-driven priority shifting, 5 retention anti-patterns, 4 improvement levers, three definitions setup. Use when measuring PMF, analyzing user retention, or deciding whether to scale or improve product.

5-question review framework (result, execution, plan, strategy, analysis), KPI propagation monitoring with 4-layer anomaly patterns, One-Way/Two-Way Door classification, withdrawal decision protocol, and assumption provenance auditing. Use during periodic reviews, buffer zone changes, or when evaluating why results diverge from expectations.

Structured root cause analysis using WHERE (MECE decomposition) then WHY (causal structure diagrams) pipeline. Includes coin-flip detection, logical-leap detection, and vicious cycle intervention. Use when buffer enters YELLOW/RED, when metrics stall, or when Actions execute but don't produce results.

Rumelt's Crux framework for building Strategy Kernels — Diagnosis (standard + reframed), Guiding Policy, Coherent Actions. Use when creating or reviewing strategic plans, when actions feel scattered, or when the founder asks "what should we focus on?"

12 startup anti-patterns with detection signals and agent responses — vanity metrics, premature scaling, sandbagging, metric switching, negative margin scaling, dead zone pricing, fundraising over product, slogans as strategy, incoherent actions, too many fronts, unwinnable battles, growth as strategy. Use as a continuous background monitor during all planning, execution, and review activities.

Unit economics health monitoring — CLV vs CAC per channel, NDR monitoring (>100% healthy, <100% leaky, target 125%+), gross margin awareness (AI API costs as real COGS), premature scaling guard (block if CAC>CLV), channel health dashboard format. Use when evaluating channel profitability, monitoring revenue health, or before scaling any acquisition channel.

Oberholzer-Gee's Value Stick — 4-layer model (Customer Delight, Firm Margin, Employee Satisfaction, Supplier Surplus), 3 diagnostic patterns (stick too short, delight giveaway, cost squeeze), "too expensive" reframe (WTP vs perception), WTS as strategic lever, complement profit pool analysis (WTP engine vs profit pool per tier). Use when pricing decisions arise, customers say "too expensive," or margin analysis is needed.

Performs a multi-agent WCAG accessibility audit of the frontend codebase. This skill should be used when the user asks to "audit accessibility", "check WCAG compliance", "run an accessibility review", "a11y audit", "check screen reader support", "fix accessibility issues", or "verify keyboard navigation", or when the transmute-pipeline agent reaches Stage 6B of the pipeline.

Audits the codebase to verify every PRD feature is fully implemented, not just scaffolded. This skill should be used when the user asks to "audit implementation completeness", "check for stubs", "detect stub components", "run implementation audit", "run Stage 5B", "verify feature completeness", or "find unfinished implementations", or when the transmute-pipeline agent reaches Stage 5B of the pipeline.

Performs a multi-agent security audit checking authentication, input validation, data exposure, and infrastructure. This skill should be used when the user asks to "audit security", "run a security review", "check for vulnerabilities", "security scan", "check auth", "find security issues", or "harden security", or when the transmute-pipeline agent reaches Stage 6A of the pipeline.

Generates a comprehensive Business Requirement Document (BRD) from a business plan using parallel agent teams. This skill should be used when the user asks to "generate BRD", "create business requirements document", "run Stage 1", "generate business requirements", "create BRD from business plan", or when the transmute-pipeline agent reaches Stage 1 of the pipeline.

Generates developer documentation (API reference, developer guide) and user-facing help docs organized by user journey. This skill should be used when the user asks to "generate documentation", "create API docs", "write developer guide", "generate help docs", "create onboarding docs", "document the codebase", or "write a changelog", or when the transmute-pipeline agent reaches Stage 6D of the pipeline.

Processes user feedback batches through the spec-update-code-test-docs chain. This skill should be used when the user asks to "process user feedback", "run the feedback loop", "analyze user feedback", "implement feedback changes", "triage support tickets", "run stage 8", "process feedback batch", or "update specs from feedback", or when the transmute-pipeline agent reaches Stage 8 of the pipeline.

Hardens error handling, network failure recovery, and edge case resilience across the product. This skill should be used when the user asks to "harden error handling", "add resilience", "handle network failures", "add retry logic", "add circuit breakers", "handle edge cases", or "improve error recovery" — or when the transmute-pipeline agent reaches Stage 6G of the pipeline.

Orchestrates full-product feature implementation using parallel backend, frontend, and test agents. This skill should be used when the user asks to "implement features", "build the product", "run feature implementation", "orchestrate implementation", "run Stage 5", "start the feature build", or "implement from PRD", or when the transmute-pipeline agent reaches Stage 5 of the pipeline.

Updates dependencies, applies security patches, and manages package versions on a regular cadence. This skill should be used when the user asks to "update dependencies", "run dependency maintenance", "check for outdated packages", "apply security patches", "update npm packages", "run stage 9", "check for vulnerabilities", or "upgrade dependencies", or when the transmute-pipeline agent reaches Stage 9 of the pipeline.

Audits and optimizes frontend, backend, and perceived performance against PRD budgets. This skill should be used when the user asks to "optimize performance", "run a performance audit", "improve page speed", "check Lighthouse scores", "fix Core Web Vitals", "reduce bundle size", "optimize queries", or "improve loading time", or when the transmute-pipeline agent reaches Stage 6C of the pipeline.

Applies visual polish and UI refinements to elevate aesthetic quality before deployment. This skill should be used when the user asks to "run visual polish", "polish the UI", "run Stage 6P", "fix visual defects", "enhance the UI", "improve the app aesthetics", "run UI refinement", "apply visual enhancements", or "fix contrast and layout issues", or when the transmute-pipeline agent reaches Stage 6P of the pipeline.

Generates a development-ready Product Requirement Document (PRD) from the BRD using parallel agent teams. This skill should be used when the user asks to "generate PRD", "create product requirements document", "run Stage 2", "generate product requirements", "create PRD from BRD", "translate BRD to PRD", or when the transmute-pipeline agent reaches Stage 2 of the pipeline.

Performs a comprehensive pre-launch verification checklist before production deployment. This skill should be used when the user asks to "run pre-launch checks", "verify launch readiness", "check production configuration", "validate deployment readiness", "generate launch checklist", "are we ready to go live", or "can we ship" — or when the transmute-pipeline agent reaches Stage 6H of the pipeline.

Performs a comprehensive frontend design elevation with interactive design discovery. This skill should be used when the user asks to "redesign the frontend", "run a design overhaul", "rebrand the UI", "run Stage 6P-R", "new visual identity", "elevate the frontend design", "run frontend redesign", "design elevation", or "replace the generic AI look", or when the transmute-pipeline agent reaches Stage 6P-R of the pipeline.

Audits the codebase for code quality issues and refactors without changing external behavior. This skill should be used when the user asks to "refactor the codebase", "clean up code quality", "eliminate duplication", "improve abstractions", "enforce consistency", "remove dead code", or "optimize architecture" — or when the transmute-pipeline agent reaches Stage 6E of the pipeline.

Auto-fixes runtime issues found during visual verification (Stage 6V) using a categorized fix-verify cycle. This skill should be used when the user asks to "run runtime remediation", "fix 6V failures", "run Stage 6R", "auto-fix verification issues", "remediate runtime issues", "fix the verification report failures", or "run the remediation cycle", or when the transmute-pipeline agent reaches Stage 6R of the pipeline.

Generates a complete project code skeleton from the PRD with full traceability to specifications. This skill should be used when the user asks to "generate project scaffolding", "scaffold the codebase", "create the code skeleton", "generate the project structure", "run Stage 3", or "scaffold from PRD", or when the transmute-pipeline agent reaches Stage 3 of the pipeline.

Generates comprehensive, realistic seed data for all environments (dev, test, demo, stress). This skill should be used when the user asks to "generate seed data", "create test data", "populate the database", "create demo data", "generate edge case data", or "set up seed scripts" — or when the transmute-pipeline agent reaches Stage 6F of the pipeline.

Runs production smoke tests to verify the deployed application works correctly in the live environment. This skill should be used when the user asks to "run production smoke tests", "verify the production deployment", "smoke test the live app", "check if production is working", "run post-deployment verification", "run stage 7V", or "verify the deployed application", or when the transmute-pipeline agent reaches Stage 7V of the pipeline.

Interactively discovers and configures the technology stack for a new product from a business plan. This skill should be used when the user asks to "discover tech stack", "configure technology stack", "select technologies", "run Stage 0", "start tech stack discovery", "define the stack", or "set up the project stack", or when the transmute-pipeline agent reaches Stage 0 of the pipeline.

Generates a user-facing documentation site from the PRD, user stories, user flows, BRD business rules, and the production application. This skill should be used when the user asks to "generate user documentation", "create the user guide", "build the Mintlify docs site", "generate user-facing docs", "create documentation for users", "run stage 7D", "generate the docs site", or "create getting started guides", or when the transmute-pipeline agent reaches Stage 7D of the pipeline.

Cross-validates BRD and PRD for coverage gaps, contradictions, and technical feasibility. This skill should be used when the user asks to "validate specs", "cross-validate BRD and PRD", "run Stage 2B", "validate specifications", "check spec consistency", "run spec validation", "verify BRD PRD alignment", or when the transmute-pipeline agent reaches Stage 2B of the pipeline.

Verifies the running application against PRD screen specs and acceptance criteria in a browser. This skill should be used when the user asks to "run visual verification", "verify the app against the PRD", "run Stage 6V", "check the running app", "verify screens match specs", "run live app verification", "test the running application", or "verify acceptance criteria in the browser", or when the transmute-pipeline agent reaches Stage 6V of the pipeline.