Agent skill · operations · pytorch
distributed-triage
Sub-triages issues in the oncall:distributed queue by assigning distributed module labels, routing to sub-oncalls, and marking triaged. Use when an issue has been routed to oncall:distributed and needs second-level triage.
Why this skill is useful
Adds 2 executable scripts for validating issue targets and labels that enhance the triaging process.
What it needs
Requires python3 installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 102,253 stars on the source repository.
What this skill does
Distributed Issue Triage Sub-Skill This sub-skill picks up where the PT-level triage bot leaves off. It processes issues that already have the oncall: distributed label and performs second-level triage: routing to a distributed sub-oncall, classifying by module, and marking triaged. Contents MCP Tools Available Reference Files Comment Deduplication Distributed Triage Steps Step 0: Already Triaged by Human Step 1: Is This Actually a Distributed Issue? Step 2: Route to Distributed Sub-Oncall Step 3: Classify Module Step 4: Type Labels Step 5: High Priority — REQUIRES HUMAN REVIEW Step 6: Missing Reproduction Constraints Distributed labels reference: See distributed-labels.json for the labels this skill is allowed to apply. ONLY apply labels from this file. Distributed triage rubric: See distributed-rubric.md for detailed routing guidance, module classification signals, and confidence calibration. Response templates: See templates.json for distributed-specific comment templates. --- MCP Tools Available Use these GitHub MCP tools for triage: Tool Purpose ------ --------- mcpgithubgetissue Get issue details and existing labels mcpgithubgetissuecomments Get existing issue comments mcpgithubupdateissue Apply labels or close issues mcpgithubaddissuecomment Add comment (only for reproduction requests or mislabel flags) mcpgithubsearchissues Find similar issues for context --- Comment Deduplication Before adding any issue comment: 1. Read the existing comments with mcpgithubgetissuecomments. 2. Check whether the triage bot has already posted the same template or a substantially equivalent request/explanation. 3. If a duplicate exists, do not add another comment. Continue with any non-comment actions that are still needed, such as labels. Treat a comment as duplicate even if the wording differs slightly or an older template version was used. For distributed triage, this includes an existing distributed reproduction request or an existing "not distributed" notice. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pytorch/distributed-triage