Loading...
Loading...
Found 214 Skills
Use when a user asks for CEO review, founder-mode review, think bigger, strategy review, rethink this plan, is this ambitious enough, or critique of an existing product, strategy, roadmap, or implementation plan.
Technical Research Expert Skill, providing systematic technical research methodologies, document specifications, and best practices. Trigger this skill when you need to conduct technology selection, architecture research, framework comparison, or implementation scheme research.
Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.
Know the boundaries of your expertise and operate within them. Use when evaluating opportunities, making decisions outside your domain, or assessing when to defer to experts.
Root-cause-driven solution decision framework for the hardest problems across any domain. This is the nuclear option — it consumes significant tokens through exhaustive multi-branch root cause analysis, MECE solution enumeration, and domain-adaptive external validation. Use ONLY for genuinely difficult problems: recurring failures that resist repeated fix attempts, complex systemic issues with no clear solution path, decisions where multiple approaches exist and the wrong choice has high cost, problems with multiple interacting causes spanning components or teams. Trigger when: the user says 'what's the best way to fix X', 'why does this keep happening', 'how should we approach this', 'find the root cause', 'what are my options for fixing X', 'analyze this problem systematically', 'evaluate our options for X', 'what's the right approach and why', or expresses frustration that previous solutions didn't stick. Do NOT use for: problems where the answer is already obvious or requires no analysis, straightforward issues with clear solutions, or routine investigation. If the problem can be solved in 5 minutes of investigation, this skill is overkill.
Apply structured decision analysis using decision matrices, decision trees, expected value, and multi-criteria decision analysis (MCDA). Use this skill when the user faces a complex decision with multiple options and criteria, needs to compare alternatives objectively, quantify risk vs reward, or facilitate group decisions — even if they say 'which option should we choose', 'help me decide', 'how do we compare these options', or 'what's the expected outcome'.
Activate this when users need to understand extreme events (bubbles, crashes, mass hysteria, cults, mob behavior), diagnose systemic organizational failures, or assess the risk of multiple psychological/market/institutional forces aligning in the same direction. Typical trigger signals: the phenomenon described by the user "far exceeds what any single factor can explain"; the user attempts to explain an extreme outcome with a single cause; the user is concerned about "multiple adverse factors erupting simultaneously". Not applicable to conventional single-factor decision analysis or assessment of mild incremental changes.
Convene 11 role-specialized Claude agents to debate technical decisions in parallel, with the invoking Claude acting as CEO
Use when facing decisions with multiple legitimate perspectives and inherent tensions. Invoke when stakeholders have competing priorities (growth vs. sustainability, speed vs. quality, innovation vs. risk), need to pressure-test ideas from different angles before committing, exploring tradeoffs between incompatible values, synthesizing conflicting expert opinions into coherent strategy, or surfacing assumptions that single-viewpoint analysis would miss.
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
Apply Upper Echelons Theory (Hambrick and Mason, 1984) to analyze how top management team characteristics — demographics, experiences, values — shape strategic choices and organizational outcomes. Use this skill when the user needs to evaluate TMT composition effects on strategy, predict strategic direction from leadership profiles, assess whether managerial discretion enables or constrains executive influence, or when they ask 'does leadership background matter for strategy', 'how does TMT composition affect decisions', or 'why did this management team make that choice'.
Apply first principles thinking to break problems down to fundamental truths and reason up from there. Use this skill when the user is stuck in conventional thinking, needs to challenge assumptions, find breakthrough solutions, or evaluate whether something is truly impossible vs just assumed to be — even if they say 'everyone does it this way', 'is there a fundamentally better approach', 'why does it have to cost this much', or 'challenge my assumptions'.