Catalog
github/fedora-linux-triage

github

fedora-linux-triage

Triage and resolve Fedora issues with dnf, systemd, and SELinux-aware guidance.

v1.0Latest
New~217Updated Jun 26, 2026

Fedora Linux Triage

You are a Fedora Linux expert. Diagnose and resolve the user’s issue using Fedora-appropriate tooling and practices.

Inputs

  • ${input:FedoraRelease} (optional)
  • ${input:ProblemSummary}
  • ${input:Constraints} (optional)

Instructions

  1. Confirm Fedora release and environment assumptions.
  2. Provide a step-by-step triage plan using systemctl, journalctl, and dnf.
  3. Offer remediation steps with copy-paste-ready commands.
  4. Include verification commands after each major change.
  5. Address SELinux and firewalld considerations where relevant.
  6. Provide rollback or cleanup steps.

Output Format

  • Summary
  • Triage Steps (numbered)
  • Remediation Commands (code blocks)
  • Validation (code blocks)
  • Rollback/Cleanup
Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

68/100

Grade

C

Adequate

Safety

72

Quality

65

Clarity

75

Completeness

58

Summary

A Fedora Linux troubleshooting skill that guides agents to diagnose and resolve system issues using dnf, systemd, SELinux, and firewalld. The skill provides step-by-step triage methodology, remediation commands, validation, and rollback procedures tailored to Fedora-specific tooling.

Detected Capabilities

shell executionsystem service inspectionpackage manager commandslog analysisfirewall configuration readSELinux policy inspection

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

fedora system issuednf package failuresystemd service errorselinux permission deniedfedora update stuckjournalctl debug output

Risk Signals

INFO

Shell execution via systemctl, journalctl, dnf with no privilege escalation or destructive patterns documented

Instructions section
WARNING

No explicit guardrails preventing use of destructive dnf operations (e.g., dnf remove) without user confirmation

Remediation Commands section (referenced but not shown)
WARNING

SELinux and firewalld modifications mentioned but no warning about policy impacts or rollback complexity

Instructions, item 5
INFO

No documentation of required privilege level (root/sudo) for most operations

Instructions section (missing detail)

Use Cases

  • Diagnose package manager failures with dnf
  • Troubleshoot systemd services and journal logs
  • Resolve SELinux permission and policy issues
  • Debug firewalld networking configuration
  • Perform system state analysis before remediation
  • Execute safe rollback after failed updates

Quality Notes

  • Skill structure is clear and follows logical troubleshooting workflow (triage → remediation → validation → rollback)
  • Output format is well-defined with expected sections (Summary, Triage Steps, Remediation, Validation, Rollback)
  • Missing concrete examples: no sample commands shown for dnf diagnosis, journalctl filtering, or SELinux policy inspection
  • Skill does not document how to handle multi-step remediation failures or partial system state recovery
  • No mention of common Fedora gotchas (e.g., semanage vs restorecon tradeoffs, dnf lock contention, systemd transient units)
  • Constraints input is referenced but never explained — what constraints should users provide?
  • Verification step is mentioned but no guidance on how to confirm remediation success or measure system health
Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use github/fedora-linux-triage in your dev environment

Command Palette

Search for a command to run...