Loading...
Loading...
Found 214 Skills
Combine multiple mental models for richer analysis. Use for complex problems requiring multiple lenses, high-stakes decisions, or when single models leave blind spots.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "ask me questions".
Run structured multi-agent debates using argue CLI for cross-examined, high-confidence answers. Use when facing strategic decisions, ambiguous trade-offs, architecture debates, or questions where multiple perspectives improve the answer. Triggers on: argue, debate, cross-examine, second opinion, multi-agent, 'Should we X or Y?' with real stakes, consensus-building, risk analysis, or confirmation-bias mitigation.
Socratic coach for breaking down problems to fundamental truths. Use when users want to think through a problem deeply, challenge assumptions, or find innovative solutions. Triggers on requests like "help me think through this", "let's break this down", "what are my blind spots", "I'm stuck on a problem", "challenge my assumptions", or explicit requests for first-principles thinking.
Simulate an expert panel discussion on a topic. Suggests 3 relevant experts/personas based on context and has them debate approaches, trade-offs, and arrive at recommendations. Use when brainstorming, exploring design decisions, or wanting multiple expert perspectives on a problem.
Use before launching products or signing contracts, when needing to combat sunk cost fallacy, or when standard pre-mortems fail to change behavior
Apply 25 professional mental models to solve complex problems. Use when: (1) facing multi-faceted challenges that require diverse perspectives, (2) stuck in single-minded approaches, (3) need innovative solutions, (4) making major decisions with multiple stakeholders, (5) understanding complex human behavior, or (6) seeking to break cognitive biases and adopt alternative viewpoints.
Guides technical decisions, architecture, and implementation. Use for tech choices, system design, API design, refactoring, or "how should I build this" questions.
Break any problem down to fundamental truths, then rebuild solutions from atoms up. Use when user says "firstp", "first principles", "from scratch", "what are we assuming", "break this down", "atomic", "fundamental truth", "physics thinking", "Elon method", "bedrock", "ground up", "core problem", "strip away", or challenges assumptions about how things are done.
Use when starting a forecast to establish a statistical baseline (base rate) before analyzing specifics. Invoke when need to anchor predictions in historical reality, avoid "this time is different" bias, or establish outside view before inside view analysis. Use when user mentions base rates, reference classes, outside view, or starting a new prediction.
Use this when you need to evaluate the risks and benefits of accepting, negotiating before accepting, pausing, or rejecting outsourcing projects, internal projects, or requirements. It is particularly suitable for scenarios with ambiguity in scope, acceptance criteria, payment terms, compliance, project timelines, or dependencies, as well as high-uncertainty situations such as emergency task insertion, contract renewal/modification, multi-requirement prioritization, or AI/LLM-related initiatives.
Trigger: Call this skill when the problem is complex, has multiple conflicting factors, unclear priorities, or you don't know what to solve first; common signals include trade-off, bottleneck, unknown root cause, unclear priority order, and mutual restraint between multiple problems. Trigger when a problem contains competing forces, unclear priorities, or no obvious entry point. Use this skill to identify contradictions, isolate the principal contradiction, classify its nature, and choose the right response.