Loading...
Loading...
Found 93 Skills
Apply first-principles thinking to break down complex problems into fundamental truths and rebuild solutions from the ground up. Use when solving strategic decisions, breaking through blockers, or challenging assumptions. Triggers on first principles, Elon Musk methodology, fundamental truths, strip assumptions, physics of the problem, rebuild from scratch.
Apply a latticework of mental models from multiple disciplines to improve decision quality. Use this skill when the user needs to think more clearly, avoid cognitive blind spots, apply cross-disciplinary reasoning, or evaluate a complex decision from multiple angles — even if they say 'how should I think about this', 'what am I missing', 'give me a different perspective', or 'what frameworks apply here'.
Use when facing complex reasoning tasks - multi-step math, logic puzzles, decisions with tradeoffs, problems where direct answers fail, or when you need to show your work. Triggers on arithmetic errors, shallow analysis, or "I'm not sure" hedging.
Iterative PDCA cycle for systematic experimentation and continuous improvement
A structured root-cause investigation protocol for complex, ambiguous, or multi-layer technical problems. Activate this skill whenever: a problem has resisted two or more fix attempts; the root cause is unknown or assumed; you are tempted to try a variation of something that already failed; a system has multiple interacting layers (hardware, OS, runtime, middleware, config, network); the user says "ultrathink", "think deeper", "figure out why", "stop guessing", "find the root cause", or "it's still broken after your fix". Also activate proactively when you catch yourself about to write a fix before you have verified the cause — that instinct is the signal the protocol is needed. The protocol enforces three disciplines that distinguish root-cause investigation from trial-and-error: (1) explicit THOUGHT/ACTION/OBSERVATION cycles, (2) a hard gate that blocks implementation until the cause is verified by direct evidence, and (3) structured escalation when in-process diagnostic tools are exhausted.
SCPR (Situation-Complication-Problem-Recommendation) framework for structured problem solving and executive communication. Use when users need to structure strategic arguments, analyze business situations, create executive summaries, or develop clear problem statements using McKinsey-style communication. Apply when structuring recommendations, writing memos, or organizing strategic thinking.
Critical-thinking brainstorming partner that acts as a requirements analyst. Use when users present ideas, feature requests, or problems they want to solve. Triggers include "I want to build", "help me validate", "users need", "I'm thinking of creating", or any request involving problem/solution validation. This skill aggressively challenges assumptions, questions perceived problems, demands evidence, and ensures solutions address genuine needs before exploring implementation.
Systematic Fishbone analysis exploring problem causes across six categories
Investigate Problem - analyzes a problem in the codebase and proposes actionable solutions