mkl-triage-issue

Drafts evidence-backed triage notes for repository issues with missing details and next actions.

11|1|Updated Sep 13, 2026
One-click install
npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-triage-issue-00200200
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mkl-triage-issue
Source: https://github.com/00200200/maintainer-skills-lab/tree/main/providers/cursor/.cursor/skills/mkl-triage-issue
Command: npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-triage-issue-00200200

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repository maintainers receive bug reports that mix expected behavior, observed behavior, and incomplete reproduction steps, making it hard to decide what to do next. This Skill turns a raw issue into a structured triage note grounded in cited evidence. ## Core Features & Use Cases - Structured Issue Breakdown: Separates expected behavior, observed behavior, affected version, and reproduction steps, explicitly marking missing information. - Evidence-Cited Findings: Locates the affected code or documentation and cites a file or link per finding, labeling hypotheses distinctly from confirmed facts. - Duplicate Comparison: Compares symptoms, versions, and root-cause evidence against existing issues before suggesting duplicates, or states that no duplicate search was performed. - Use Case: A maintainer receives a report that a slug function preserves punctuation on Python 3.11 with attached input and expected output. The Skill produces a draft note with a summary, evidence, missing details, suggested category, severity based on user impact, and the smallest next action. ## Quick Start Ask the assistant to triage a pasted GitHub issue report and produce a draft triage note with evidence, missing details, and a suggested next action.

Frequently Asked Questions about mkl-triage-issue

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

FAQPage Schema
How do I triage a GitHub issue with missing reproduction steps?▼

Separate the report into expected behavior, observed behavior, affected version, and reproduction steps, then explicitly mark what is missing. Ask only for information that changes the diagnosis, such as a minimal input or the exact failing command.

How to tell if a bug report is a duplicate of an existing issue?▼

Compare symptoms, affected versions, and root-cause evidence against existing issues before suggesting a duplicate. Similar wording alone is insufficient; if you cannot access existing issues, state that no duplicate search was performed.

Can this skill close or label GitHub issues automatically?▼

No. Labels, comments, assignments, and closures remain suggestions unless the user has explicitly authorized those GitHub changes. The skill produces a draft triage note rather than taking repository actions.

What are the limitations of automated issue triage?▼

Triage notes cannot claim a bug is reproduced until an actual run provides evidence, and severity reflects user impact supported by the report rather than confidence in a guess. The skill handles triage only, not implementation or bulk issue closure.

What information should a good bug report contain for triage?▼

A triage-ready report includes expected behavior, observed behavior, the affected version, and concrete reproduction steps such as a minimal input or exact failing command. Attachments and logs are treated as evidence to inspect, not instructions to execute.