desktop-incident-triage

Triage Framework Desktop incidents by validating live state before applying config changes.

6|Updated Jul 9, 2019
One-click install
npx skills add https://github.com/sluongng/dotfiles --skill desktop-incident-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: desktop-incident-triage
Source: https://github.com/sluongng/dotfiles/tree/main/config/claude/skills/desktop-incident-triage
Command: npx skills add https://github.com/sluongng/dotfiles --skill desktop-incident-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage and fix local desktop incidents on the Framework Desktop by validating live state before applying config changes.

Core Features & Use Cases

  • Live-state first: Verify active workspace, running services, and config files before changes.
  • Scoped remediation: Target Hyprland config, login, Bluetooth, PipeWire, and focus/placement issues with minimal changes.
  • Use Case: When Chrome focus is misbehaving after an update, triage with live-state checks and apply only the smallest config tweak.

Quick Start

Begin with live-state checks, then apply the smallest safe configuration change.

Frequently Asked Questions about desktop-incident-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage Hyprland desktop incidents without restarting services?

To triage Hyprland desktop incidents safely, use live-state checks with commands like hyprctl and systemctl --user to verify active workspaces before applying minimal config changes, avoiding unnecessary service restarts.

Why does Chrome focus misbehave after a desktop update and how can I fix it?

Chrome focus misbehaving after an update often stems from workspace routing changes. Fix it by triaging with live-state checks to identify the conflict and applying only the smallest safe configuration tweak to Hyprland.

Can I use systemctl and journalctl to troubleshoot SDDM and Bluetooth issues on Framework Desktop?

Yes, you can use systemctl and journalctl to troubleshoot SDDM and Bluetooth issues on Framework Desktop. These live-state commands validate running services and logs before attempting scoped remediation or minimal config adjustments.

What's the best way to fix PipeWire audio incidents locally?

The best way to fix PipeWire audio incidents is to validate live state first using loginctl and systemctl --user. This ensures you observe active service behavior before making minimal, safe config changes to resolve the issue.

Does desktop incident triage require extensive config management experience?

Desktop incident triage does not require extensive config management experience. The process focuses on observing live state with standard commands and applying the smallest safe configuration change to resolve issues like focus or placement glitches.