issue-triage

Analyzes GitHub issues for SLA violations, safety concerns, and duplicates, producing a markdown report.

4.5k|777|Updated Mar 10, 2025
One-click install
npx skills add https://github.com/modelcontextprotocol/csharp-sdk --skill issue-triage-modelcontextprotocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/modelcontextprotocol/csharp-sdk/tree/main/.github/skills/issue-triage
Command: npx skills add https://github.com/modelcontextprotocol/csharp-sdk --skill issue-triage-modelcontextprotocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps maintainers quickly assess and prioritize open issues in GitHub repositories, ensuring timely triage, SLA compliance, and risk mitigation.

Core Features & Use Cases

  • Issue analysis and prioritization: Automatically evaluates issues based on labels, age, and status to identify urgent, stale, or missing labels.
  • SLA compliance monitoring: Checks whether issues are triaged within Tier 1 or Tier 2 SLA thresholds and flags violations.
  • Comprehensive reporting: Generates detailed markdown reports with summaries, safety warnings, and recommendations for action, suitable for project management.
  • Use Case: When asked to audit a large repository, produce an organized report highlighting critical issues, including potential duplicates and cross-repository linkages, to guide developer focus.

Quick Start

Provide the link to your GitHub repository, and the skill will analyze all open issues, generate a detailed triage report, and identify areas needing immediate attention.

Frequently Asked Questions about issue-triage

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

FAQPage Schema
How do I prioritize GitHub issues and identify SLA violations across repositories?

To prioritize GitHub issues and identify SLA violations, you can analyze open issues based on labels, age, and status to flag urgent items, stale threads, and missing labels. This generates a detailed markdown report with safety warnings and actionable recommendations.

What is the best way to audit a large backlog of GitHub issues for duplicates?

Auditing a large backlog of GitHub issues for duplicates involves analyzing open issues to find cross-repository linkages and potential overlaps. This process produces an organized triage report highlighting critical issues to guide developer focus and mitigate risks.

Can I automatically generate a markdown triage report for unmanaged GitHub issues?

Yes, you can automatically generate a markdown triage report for unmanaged GitHub issues. By evaluating issues against Tier 1 or Tier 2 SLA thresholds, the analysis produces a comprehensive summary of critical issues, safety concerns, and prioritization recommendations.

Does this issue triage approach work for monitoring Tier 1 and Tier 2 SLA compliance?

Yes, this issue triage approach works for monitoring Tier 1 and Tier 2 SLA compliance. It checks whether issues are triaged within the specified SLA thresholds, flags violations, and outputs a detailed markdown report suitable for project maintainers managing large backlogs.

How do I find GitHub issues with missing labels or safety concerns in my repository?

To find GitHub issues with missing labels or safety concerns, you analyze the repository to automatically evaluate issue metadata. The resulting markdown report flags urgent issues, identifies missing labels, and highlights safety warnings to ensure timely triage and risk mitigation.