⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
problem-solving
>
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Problem Solving
Structured problem diagnosis and resolution methodology for OpenClaw.
Features
- 🔍 Systematic Diagnosis: Map call chains and trace data flow end-to-end
- 🎯 Root Cause Analysis: Three-question framework to confirm true causes
- 🛠️ Solution Design: Compare multiple approaches on effectiveness, risk, and reversibility
- ✅ Rigorous Verification: Multi-level testing including regression checks
- 📝 Post-Mortem Reviews: Extract learnings to prevent recurrence
When to Use
Use this skill when:
- Problem cause is unclear and requires investigation
- A previous fix attempt failed
- Issue involves multiple components interacting
- Modifications carry risk or side effects
- You'd need to say "可能是..." to explain the cause
Skip for:
- Obvious one-liner fixes
- Clear error messages with known solutions
- User says "just fix it" for simple issues
The Process
- Define: Turn vague symptoms into precise problem statements
- Diagnose: Trace data flow, verify each step, confirm root cause
- Design: Generate and compare at least 2 solution candidates
- Execute: Change one variable at a time with rollback plan
- Verify: Reproduce trigger, check regressions, test durability
- Review: Extract lessons for future prevention
Installation
Via ClawHub (Recommended)
clawhub install problem-solving
Manual Installation
Clone to ~/.openclaw/skills/problem-solving
Usage
The skill activates automatically when appropriate. You can also explicitly request it:
帮我分析一下这个问题
Use structured problem solving for this issue
Let's diagnose this systematically
Anti-Patterns to Avoid
- Guess-and-fix: See symptom → change immediately
- Surface fix: Change bad value without asking why
- Multi-change: Change 3 things at once
- Premature victory: "Should be fixed" without verification
License
MIT License - see LICENSE file
// HOW IT'S BUILT
KEY FILES