Explore skills

Product fitness and solution validation for bootstrapped founders. Assesses whether THIS specific solution is the right way to address a validated problem — value proposition clarity, solution-problem fit, minimum product achievability, differentiation reality, switching motivation, time-to-value, retention potential, and substitute vulnerability. Use when user runs `/solution-analysis`, asks abou

Quick SWOT analysis with bootstrapper lens. Produces a structured strengths/weaknesses/opportunities/threats matrix with evidence, strategic implications, and action priorities. Use when user runs `/swot`, asks for "SWOT analysis", "strengths and weaknesses", "strategic overview", "quick business assessment", or needs a fast strategic snapshot before deeper analysis.

Market timing and entry window assessment for bootstrapped founders. Evaluates whether the moment is right — strategic inflection points, adoption stage, buyer behavior shifts, regulatory catalysts, incumbent vulnerability windows, and bootstrapper timing fit. Use when user runs `/timing-analysis`, asks about "why now", "market timing", "is it too late", "is it too early", "entry window", "inflect

ICP and buyer persona card generator for bootstrapped founders. Produces 2-3 detailed persona cards (primary buyer, secondary buyer, anti-persona) with demographics, psychographics, behavior patterns, pain story, buying triggers, objections, and targeting criteria. Includes beachhead drift check. Use when user runs `/user-personas`, asks about "who is my customer", "buyer persona", "ICP", "ideal c

Brutal, bullshit-free business strategist and mentor for founders. Use when user runs `/venture-sensei`, asks to "critique my startup", "review my business idea", "give me startup advice", "what customer acquisition strategy", "help me create an offer", "validate this idea", or needs strategic business mentorship. Created by the founders of RevenueHunt.com.

Use when you want to audit project dependencies — scans all lockfiles for CVEs, outdated major versions, and license violations. Run before releases or periodically as a health check.

Use when you are about to create a git commit — generates a conventional commit message with type(scope): TICKET description format. Auto-detects ticket from branch name or arguments. Always use this instead of running git commit directly.

Use when you encounter a bug, error, or unexpected behavior during a task — follows a reproduce → isolate → fix → verify cycle. Invoke this instead of guessing at a fix.

Use when you want to audit environment variable usage — scans the entire codebase for all env var references across all sources (code, Docker, CI, config files) and flags anything undocumented or inconsistent. Works for any stack and any env var pattern.

Use when starting work on a GitHub or Jira issue — reads the issue, explores affected code, and produces a ready-to-execute implementation plan. Invoke this at the start of any ticket-driven task instead of jumping straight to /plan.

Use at the start of a session on an unfamiliar or returning project — reads architecture docs, recent activity, open work, and coding conventions to prime context before starting any task. Invoke this before /plan or /issue when you haven't worked on the project recently.

Use when a file or module has grown too complex — removes unnecessary abstractions, dead code, and over-engineering without changing behavior. Invoke after implementing a feature when the code feels over-engineered.