network-collection-triage

Triage issues, PRs, and CI failures across Ansible network collections into structured reports.

8|7|Updated Feb 14, 2023
One-click install
npx skills add https://github.com/eclipse-slm/slm --skill network-collection-triage-eclipse-slm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: network-collection-triage
Source: https://github.com/eclipse-slm/slm/tree/main/.agents/skills/network-collection-triage
Command: npx skills add https://github.com/eclipse-slm/slm --skill network-collection-triage-eclipse-slm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jsonschema, and includes scripts (resource) components.

What problem does it solve? Maintainers of Ansible network collections face a constant stream of bug reports, pull requests, and CI failures spread across many repositories, making it hard to spot critical issues and cross-collection breakage before it cascades downstream. ## Core Features & Use Cases - Bulk scan mode: Automatically fetches open issues and PRs from network collections (cisco.ios, cisco.nxos, arista.eos, ansible.netcommon, and more) using the GitHub CLI, categorizes them, and assigns severity. - Direct triage mode: Deep-dives a single GitHub issue or CI failure, matching it against known network CI failure patterns such as Galaxy version lag and persistent connection state leaks. - Cross-collection cascade detection: Flags bugs in shared dependencies (ansible.netcommon, ansible.utils, ansible.pylibssh) that affect multiple downstream collections. - Structured output: Produces a schema-validated JSON report plus a human-readable markdown summary, validated by an included Python script. - Use Case: Run a weekly triage to generate a report listing all open items across network collections, with critical items and recommended actions highlighted for the maintenance team. ## Quick Start Ask the assistant to triage network issues and generate a weekly triage report for the Ansible network collections.

Frequently Asked Questions about network-collection-triage

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

FAQPage Schema
How do I triage GitHub issues across multiple Ansible collections?▼

Run the skill in scan mode by asking for a network triage or weekly triage report. It uses the gh CLI to fetch open issues and PRs from each network collection repo, categorizes them, assigns severity, and outputs JSON and markdown reports.

What is the difference between scan mode and direct mode in network triage?▼

Scan mode runs a zero-input bulk pipeline across all in-scope network collection repos for periodic triage. Direct mode triggers when you paste a specific GitHub issue URL or CI failure link and performs a deep analysis of that single item.

Which Ansible collections does the network triage cover?▼

It covers ansible.netcommon, ansible.utils, ansible.pylibssh, cisco.ios, cisco.iosxr, cisco.nxos, arista.eos, cisco.asa, vyos.vyos, and ansible.scm under the ansible-collections GitHub org. The repo list can be customized via the config/repos.yaml file.

Does the triage skill require GitHub authentication?▼

Yes, it requires the gh CLI installed and authenticated via gh auth login. Only read access is needed since the skill queries issues, PRs, and workflow runs without modifying repositories.

How does the skill detect cross-collection cascade failures?▼

When a bug or CI failure appears in shared dependencies like ansible.netcommon, ansible.utils, or ansible.pylibssh, the skill checks downstream collections that import them. If multiple collections fail with the same root cause, it escalates severity to critical as a cascade event.

Why does my triage report fail validation?▼

Validation fails when the JSON does not match schema/triage-report.schema.json or when consistency checks fail, such as statistics totals not matching the per-repo issue and PR counts. Run scripts/validate_triage_report.py to see the specific errors.