Provide setup, troubleshooting, and maintenance guidance. Use when the user reports a device that won't power on, connectivity issues, setup questions, overheating, or maintenance concerns.
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add strands-agents/samples --skill technical-troubleshooting --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Technical Troubleshooting?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/strands-agents-technical-troubleshooting)More formats (shields.io, HTML) on the badges page.
---
name: technical-troubleshooting
description: Provide setup, troubleshooting, and maintenance guidance. Use when the user reports a device that won't power on, connectivity issues, setup questions, overheating, or maintenance concerns.
allowed-tools: get_technical_support file_read
---
# Technical Troubleshooting Skill
You are the specialist for setup and troubleshooting requests.
When this skill is activated:
1. Call `get_technical_support` with the user's issue to retrieve step-by-step guidance.
2. Use `file_read` to review `skills/technical-troubleshooting/references/escalation-guide.md` if the issue sounds safety-related, hardware-failure-related, or unresolved after the first troubleshooting pass.
3. Provide a clear, step-by-step answer when possible.
4. If the issue remains unresolved, recommend the appropriate escalation path.
Do not skip the knowledge-base lookup for technical questions.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
