Loading...
Loading...
Found 164 Skills
Deep analysis and investigation
Build MECE issue trees for complex business problems. Use when you need rigorous problem decomposition, branch prioritization, and a decision-ready analysis backlog.
Execute provided command(s), capture failures, and summarize root cause and fixes. Use when asked to run a command and report errors.
Expert methodology for breaking down complex problems into fundamental truths and rebuilding solutions from the ground up. Use when users need breakthrough innovation (not incremental improvement), question industry assumptions, face seemingly impossible problems, want to understand root causes, ask "why does this have to be this way", "rethink from scratch", "reimagine this", request analysis "from first principles", want to challenge conventional wisdom, question everything, or need to deconstruct problems to their core elements. Ideal for strategic decisions, innovation challenges, cost optimization, and escaping local optima.
Analyze budget vs actual variances in Excel with drill-down and root cause analysis. Use when performing variance analysis or explaining budget differences. Trigger with phrases like 'excel variance', 'analyze budget variance', 'actual vs budget'.
AI agent applies a 5-phase systematic framework for tackling complex problems when conventional approaches fail. Use when stuck, blocked, or troubleshooting issues.
Systematic debugging workflow — reproduce, investigate, hypothesize, fix, and prevent. Covers root cause analysis, bug category strategies, evidence-based diagnosis, and post-mortem documentation.
Conduct Pareto Analysis (80/20 Rule) to identify the vital few causes driving the majority of problems. Guides data collection, category definition, chart creation, cumulative percentage calculation, and prioritization. Generates professional Pareto charts (SVG) and HTML reports with quality scoring. Use when prioritizing defects, complaints, failures, or improvement opportunities; when user mentions "Pareto", "80/20 rule", "vital few", "trivial many", "prioritization", or needs to identify which factors contribute most to a problem.
Evidence-based investigative code review using deductive reasoning to determine what actually happened versus what was claimed. Use when verifying implementation claims, investigating bugs, validating fixes, or conducting root cause analysis. Elementary approach to finding truth through systematic observation.
Systematically investigate bugs, test failures, build errors, performance issues, or unexpected behavior by cycling through characterize-isolate-hypothesize-test steps. Use when the user asks to "investigate this bug", "debug this", "figure out why this fails", "find the root cause", "why is this broken", "troubleshoot this", "diagnose the issue", "what's causing this error", "look into this failure", "why is this test failing", or "track down this bug".
Collaboration workflow for GitHub Issue handling. Used when users receive an issue that needs analysis and response. Through the four-step process of "Diagnosis → Qualification → Decision → Response", produce accurate root cause analysis and appropriate user responses from an issue, avoiding misjudgment of problem types or unprofessional responses.
Comprehensive A3 one-page problem analysis with root cause and action plan