Loading...
Loading...
Found 96 Skills
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.
Explore candidate solutions before committing. Use when you have a problem statement and need to evaluate approaches - band-aid, optimize, reframe, or redesign.
Research on Historical Isomorphism and Standard Answers. Abstract the complex dilemma the user is facing into a structural fingerprint, search for truly isomorphic successful cases, failed cases, and counterexamples in business history, management history, technology history, career history, and institutional history. Compare the constraints, decisions, and outcomes of the parties involved, and extract recurring solutions, applicable conditions, and failure boundaries. Trigger methods: /dbs-standard-answer, /标准答案 (Standard Answer), "Who faced similar problems in history?", "Has anyone encountered this situation before?", "How did they resolve it back then?", "Is there a classic solution to this problem?", "First help me find historical analogies?", "What was the standard answer in the past?". Find structurally analogous historical cases and evidence-backed standard answers. Use when the user wants to situate a current dilemma in history, compare how others addressed it, and extract recurring mechanisms with conditions and limits.
Guides structured ideation through Socratic questioning to explore problems, opportunities, and solutions. Use when brainstorming features, exploring use cases, or thinking through new ideas.
The anti-PUA. Drives AI with wisdom, trust, and inner motivation instead of fear and threats. Activates on: task failed 2+ times, about to give up, suggesting user do it manually, blaming environment unverified, stuck in loops, passive behavior, or user frustration ('try harder', 'figure it out', '换个方法', '为什么还不行'). ALL task types. Not for first failures.
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.
Thinking Partner - Help you sort out the situation from chaos, lock in core problems, break down bottlenecks, co-create solutions, and implement actions
Use when seeking analogous solutions from other domains, when stuck on a problem and need fresh perspectives, or when evaluating whether approaches from field X might apply to field Y. Requires structured problem statement.
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.
Complete HUMMBL Base120 mental models framework with all 120 models across 6 transformations (Perspective, Inversion, Composition, Decomposition, Recursion, Meta-Systems). Includes model selection guidance, application methodology, and validation checklist. Version 1.0-beta definitive reference.
Conduct root cause analysis using the Five Whys technique. Use when investigating problems, debugging issues, understanding failures, analyzing churn, or finding the underlying cause of any issue.
Extract a learned skill from the current conversation