From linux-packaging
Use when a local application, CLI tool, or service on the user's Linux workstation isn't working and needs interactive debugging. Triggers on phrases like "X isn't working", "debug X", "X is broken", "fix X on my machine", "troubleshoot X".
How this skill is triggered — by the user, by Claude, or both
Slash command
/linux-packaging:debug-local-toolThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interactive debugging skill for when a local tool, application, or service on the user's workstation isn't behaving correctly.
Interactive debugging skill for when a local tool, application, or service on the user's workstation isn't behaving correctly.
lsb_release -a if needed)Work interactively with the user. Don't dump a wall of "try this, try that" — investigate systematically:
Ask the user (if not already clear):
Run these as appropriate — don't run all of them blindly, pick what's relevant:
# Is it installed?
which <tool> || dpkg -l | grep <tool> || flatpak list | grep -i <tool> || snap list | grep <tool>
# What version?
<tool> --version
# Is a service involved?
systemctl status <service>
journalctl -u <service> --no-pager -n 50
# Process running / stuck?
pgrep -a <tool>
# Recent logs
journalctl --user -n 100 --no-pager | grep -i <tool>
# Desktop app crash?
coredumpctl list | tail -10
# Permissions?
ls -la $(which <tool>)
# Dependencies?
ldd $(which <tool>) | grep "not found"
# Package integrity
dpkg -V <package> 2>/dev/null
# Flatpak/Snap specific
flatpak info <app-id>
snap info <snap-name>
Many issues on this system are Wayland-related. Check:
--ozone-platform=wayland or similar flags? (Electron apps)xdg, xdotool, xclip dependencies that need Wayland equivalents (wl-copy, wl-paste, ydotool)XDG_SESSION_TYPE is wayland--enable-features=UseOzonePlatform --ozone-platform=wayland| Symptom | Likely cause |
|---|---|
| App launches but blank/black window | Wayland compatibility, try with QT_QPA_PLATFORM=xcb or Electron flags |
| Clipboard not working | Using xclip instead of wl-copy/wl-paste |
| Screen recording fails | Missing PipeWire portal, xdg-desktop-portal-kde not running |
| GPU/ROCm tool fails | Wrong gfx target, check HSA_OVERRIDE_GFX_VERSION |
| Audio tool fails | PipeWire issue, check wpctl status, pw-cli ls |
| Segfault on launch | Missing lib, check ldd, check coredump |
| "Permission denied" | Flatpak sandbox, snap confinement, or missing group membership |
| Python tool broken | Wrong Python version or venv, check which python3, pip path |
| Node tool broken | Wrong Node version, check node -v, nvm status |
After a successful fix, create a GitHub gist documenting what happened:
/tmp/fix-<tool-name>.md with this structure:# Fix: <Tool Name> — <Brief Description of Issue>
**Date:** YYYY-MM-DD
**System:** Ubuntu <version>, KDE Plasma, Wayland
**Tool:** <tool name and version>
## Problem
<What wasn't working, including error messages>
## Root Cause
<Why it was broken>
## Fix
<Exact commands/changes that fixed it>
## Verification
<How we confirmed it works>
## Notes
<Anything useful for future reference — e.g., "this may recur after kernel updates">
# Private (default):
gh gist create -d "Fix: <tool> — <brief issue>" /tmp/fix-<tool-name>.md
# Public (if user requests):
gh gist create -p -d "Fix: <tool> — <brief issue>" /tmp/fix-<tool-name>.md
journalctl is your friend.npx claudepluginhub danielrosehill/claude-code-plugins --plugin linux-packagingGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.