Source profileQuality 58/100

github/awesome-copilot/skills/fedora-linux-triage/SKILL.md

fedora-linux-triage

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

Source repository stars
37,126
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/github/awesome-copilot --skill "skills/fedora-linux-triage"
    Safe inspection promptEditorial

    Inspect the Agent Skill "fedora-linux-triage" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/fedora-linux-triage/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      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 firewall…

      Confirm Fedora release and environment assumptions.Provide a step-by-step triage plan using systemctl, journalctl, and dnf.Offer remediation steps with copy-paste-ready commands.
    2. 02

      Inputs

      ${input:FedoraRelease} (optional)

      ${input:FedoraRelease} (optional)${input:ProblemSummary}${input:Constraints} (optional)
    3. 03

      Output Format

      Summary

      SummaryTriage Steps (numbered)Remediation Commands (code blocks)

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score58/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars37,126SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guidecatalog recordEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    github/awesome-copilot
    Skill path
    skills/fedora-linux-triage/SKILL.md
    Commit
    9933dcad5be5caeb288cebcd370eeeb2fc2f1685
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    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