linux-troubleshooting
Linux system troubleshooting workflow for diagnosing and resolving system issues, performance problems, and service failures.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- linux-troubleshooting
- risk
- safe
- source
- personal
- category
- granular-workflow-bundle
- date_added
- 2026-02-27
- description
- Linux system troubleshooting workflow for diagnosing and resolving system issues, performance problems, and service failures.
03 SKILL.md 正文
Linux Troubleshooting Workflow
Overview
Specialized workflow for diagnosing and resolving Linux system issues including performance problems, service failures, network issues, and resource constraints.
When to Use This Workflow
Use this workflow when:
- Diagnosing system performance issues
- Troubleshooting service failures
- Investigating network problems
- Resolving disk space issues
- Debugging application errors
Workflow Phases
Phase 1: Initial Assessment
Skills to Invoke
bash-linux- Linux commandsdevops-troubleshooter- Troubleshooting
Actions
- Check system uptime
- Review recent changes
- Identify symptoms
- Gather error messages
- Document findings
Commands
uptime
hostnamectl
cat /etc/os-release
dmesg | tail -50
Copy-Paste Prompts
Use @bash-linux to gather system information
Phase 2: Resource Analysis
Skills to Invoke
bash-linux- Resource commandsperformance-engineer- Performance analysis
Actions
- Check CPU usage
- Analyze memory
- Review disk space
- Monitor I/O
- Check network
Commands
top -bn1 | head -20
free -h
df -h
iostat -x 1 5
Copy-Paste Prompts
Use @performance-engineer to analyze system resources
Phase 3: Process Investigation
Skills to Invoke
bash-linux- Process commandsserver-management- Process management
Actions
- List running processes
- Identify resource hogs
- Check process status
- Review process trees
- Analyze strace output
Commands
ps aux --sort=-%cpu | head -10
pstree -p
lsof -p PID
strace -p PID
Copy-Paste Prompts
Use @server-management to investigate processes
Phase 4: Log Analysis
Skills to Invoke
bash-linux- Log commandserror-detective- Error detection
Actions
- Check system logs
- Review application logs
- Search for errors
- Analyze log patterns
- Correlate events
Commands
journalctl -xe
tail -f /var/log/syslog
grep -i error /var/log/*
Copy-Paste Prompts
Use @error-detective to analyze log files
Phase 5: Network Diagnostics
Skills to Invoke
bash-linux- Network commandsnetwork-engineer- Network troubleshooting
Actions
- Check network interfaces
- Test connectivity
- Analyze connections
- Review firewall rules
- Check DNS resolution
Commands
ip addr show
ss -tulpn
curl -v http://target
dig domain
Copy-Paste Prompts
Use @network-engineer to diagnose network issues
Phase 6: Service Troubleshooting
Skills to Invoke
server-management- Service managementsystematic-debugging- Debugging
Actions
- Check service status
- Review service logs
- Test service restart
- Verify dependencies
- Check configuration
Commands
systemctl status service
journalctl -u service -f
systemctl restart service
Copy-Paste Prompts
Use @systematic-debugging to troubleshoot service issues
Phase 7: Resolution
Skills to Invoke
incident-responder- Incident responsebash-pro- Fix implementation
Actions
- Implement fix
- Verify resolution
- Monitor stability
- Document solution
- Create prevention plan
Copy-Paste Prompts
Use @incident-responder to implement resolution
Troubleshooting Checklist
- [ ] System information gathered
- [ ] Resources analyzed
- [ ] Logs reviewed
- [ ] Network tested
- [ ] Services verified
- [ ] Issue resolved
- [ ] Documentation created
Quality Gates
- [ ] Root cause identified
- [ ] Fix verified
- [ ] Monitoring in place
- [ ] Documentation complete
Related Workflow Bundles
os-scripting- OS scriptingbash-scripting- Bash scriptingcloud-devops- DevOps
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.