Loading...
Loading...
Found 118 Skills
Apply Edward de Bono's parallel thinking framework (1985) to make better decisions by examining ideas from six distinct perspectives systematically. Use when: **Making complex decisions** that require multiple perspectives; **Evaluating new products, offers, or strategies** before launch; **Breaking out of analysis paralysis** with structured thinking; **Running productive meetings** where everyone thinks in the same direction; **Balancing optimism with caution** in strategic planning
Apply structured thinking and MECE principle to break down complex problems. Use at the start of any strategic analysis to organize thoughts and create compelling arguments.
TRIZ systematic innovation methodology with AI-enhanced prompts. Use when: (1) Technical contradiction - improve A but B worsens, (2) Physical contradiction - need opposite properties, (3) Cross-industry solutions via FOS/MOS, (4) Technology evolution prediction, (5) Complex engineering problems. Triggers: "TRIZ", "contradiction", "inventive", "trade-off", "improve without worsening", "ข้อขัดแย้งทางเทคนิค", "innovation breakthrough"
Identify motif-level structures in a piece of information, expand abstract relationships back into concrete observable phenomena, and then use wind tunnel testing to verify key causal relationships and boundaries. USE WHEN user says 'find structure', 'what is the motif', 'structure wind tunnel', 'underlying structure', 'don’t just do AB testing', or wants to explore the generative mechanism behind a problem. Only expand cross-domain sources or multi-motif combinations when explicitly requested by the user. NOT FOR general summaries, single analogies, factual queries, or execution tasks with a clear unique solution.
Guides structured ideation through Socratic questioning to explore problems, opportunities, and solutions. Use when brainstorming features, exploring use cases, or thinking through new ideas.
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly. Use this skill whenever a user says "help me think through X", "challenge my thinking", "what am I missing", "apply mental models to this", "play devil's advocate", "stress test this idea", "poke holes in my plan", "help me decide between X and Y", "what are the second-order effects", "I'm stuck on a decision", names any specific model (SWOT, first principles, inversion, pre-mortem, etc.), or asks for structured reasoning on any ambiguous, high-stakes, or complex problem. Also trigger when the user seems uncertain, is rationalizing, or is asking "am I thinking about this right?" Even casual phrases like "what do you think about..." on non-trivial topics should trigger this skill.
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.
Use the 'Dialysis Prism' framework to penetrate the surface of problems and identify their root causes. Resolve persistent recurring issues through three steps: calibrating Goal B, reconstructing Method A, and eliminating Variable C. It applies to scenarios where the same problem keeps recurring despite various attempted solutions, as well as analytical scenarios that require precise problem definition before resolution. Use this skill when you find that 'patchwork' solutions are ineffective. It is not suitable for scenarios in entirely new fields with no historical methods to reference, nor for purely uncertain events (which fall under the probability/risk domain and require the use of mirror-world). Key trigger signals: 'Why does this problem happen again?', 'Why can't we solve it for good?', 'I've tried so many methods but none work', 'What exactly is the root cause of this problem?'
McKinsey Consultant-style Problem Solving System. Starting from business problems, it generates McKinsey-style research reports and PPTs through hypothesis-driven structured analysis methods. It integrates Problem Solving methodology, MECE principles, Issue Tree decomposition, Hypotheses formulation, Dummy Page design, intelligent data collection, and professional PPT generation capabilities.
"Invert, always invert." Apply Carl Jacobi's mathematical principle and Charlie Munger's investing wisdom to solve problems by thinking backward from failure. Use when: **Goal setting** - Define what would guarantee failure, then avoid it; **Risk analysis** - Identify what could destroy your project before starting; **Decision making** - Evaluate choices by examining their worst outcomes; **Problem solving** - When direct approaches aren't working, reverse the question; **Strategy development...
Analyze complex systems from elements to relationships, from parts to the whole, and from static to dynamic perspectives. Suitable for scenarios where problems recur, where a single change affects the entire system, and where treating symptoms doesn't work. When you find that 'the harder you work, the worse it gets' or 'problems keep recurring', you need to switch to systematic thinking to find root solutions. Not applicable to simple single-cause problems or emergency scenarios requiring quick action. Key trigger signals: 'Why does this problem keep recurring?', 'Fixing A broke B instead', 'Feeling stuck in a loop'.
When a solution seems impossible and the path forward is blocked — the antidote to any roadblock or wall. Refuses to take no for an answer: classifies what kind of "no" you actually hit, then runs targeted lateral-thinking techniques (assumption autopsy, inversion, first principles, constraint toggling, analogical transfer, and more from a 10-technique inventory) until the wall cracks or is proven load-bearing. Generates a minimum of 10 angles before evaluating any. AGENTS: use this on yourself mid-task — when an API doesn't support what you need, an approach has failed twice, or a "that's not possible" / "the only option is" sentence is forming in your response, run the fast path BEFORE reporting a dead end; every dead-end report should arrive with tried-angles receipts. Archives every wall to ~/.config/makerskills/unstuck/archive/ so you learn which techniques crack YOUR walls. Sits upstream of decide: turns "impossible" into 2–3 viable angles, then decide picks one. Triggers on "/unstuck," "I'm stuck," "this seems impossible," "we hit a wall," "there's no way to," "they said no," "dead end," "out of options," "I've tried everything," "work around this," "think outside the box."