New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Triage Issues

by dyoshikawa in dyoshikawa/rulesync

Triage open GitHub issues by reviewing unlabeled ones and applying the most appropriate labels based on their content

MITAuto-check passedDevelopment

Install Triage Issues

skills CLI
$ npx skills add dyoshikawa/rulesync --skill triage-issues -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dyoshikawa/rulesync triage-issues --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dyoshikawa/rulesync.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.rulesync/skills/triage-issues .claude/skills/triage-issues && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
triage-issues
GitHub stars
1.5k
Token cost
~896 tokens
SKILL.md length
443 words
Files
1
Skills in repo
40
Repo updated
First seen
Licence
MIT

At a glance

Triage open GitHub issues by reviewing unlabeled ones and applying the most appropriate labels based on their content

  • Works in 6 steps: List Available Labels → Find Unlabeled Open Issues → Gather Context per Issue → …
  • Tasks that involve Issue triage
  • SKILL.md covers Step 1: List Available Labels, Step 2: Find Unlabeled Open…, Step 3: Gather Context per Issue and Step 4: Decide the Labels, plus 2 more sections
  • Calls gh

What it does

Triage Issues is an agent skill from dyoshikawa/rulesync. Triage open GitHub issues by reviewing unlabeled ones and applying the most appropriate labels based on their content

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Issue triage. It works with GitHub. The repository describes itself as: A Utility CLI for AI Coding Agents. The licence is MIT.

When your agent uses it

  • Tasks that involve Issue triage

Example prompts

  • “/triage-issues”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. List Available Labels
  2. Find Unlabeled Open Issues
  3. Gather Context per Issue
  4. Decide the Labels
  5. Apply the Labels
  6. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 2c577d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Triage Issues loads about 896 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 443 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~896

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dyoshikawa/rulesync at commit 2c577d0, republished under its MIT licence (© dyoshikawa). 443 words, ~896 tokens.

Download SKILL.mdSave it as .claude/skills/triage-issues/SKILL.md (or your agent's skills folder).
name
triage-issues
description
Triage open GitHub issues by reviewing unlabeled ones and applying the most appropriate labels based on their content
targets
*

Triage Open Issues

Review all open GitHub issues that currently have no labels and apply the most appropriate labels based on their content.

Step 1: List Available Labels

Fetch the full list of labels defined in this repository so the triage stays within the known label set:

bash
gh label list --limit 100

Treat this list as the authoritative vocabulary. Do not invent new labels.

Step 2: Find Unlabeled Open Issues

Fetch all open issues that have no labels attached:

bash
gh issue list --state open --search "no:label" --limit 100 --json number,title,author,url

If the result is empty, report that nothing needs triage and stop.

Step 3: Gather Context per Issue

For each unlabeled issue, read the description and the discussion so the label choice is grounded in the actual content:

bash
gh issue view <issue_number>
gh issue view <issue_number> --comments

Run these in parallel across issues where practical.

Step 4: Decide the Labels

For each issue, pick the labels that best describe it. Typical signals:

  • bug — something is broken or behaves incorrectly.
  • enhancement — a new feature, new tool/feature support, or a capability request.
  • documentation — docs, README, or docs/**/*.md changes.
  • refactoring — internal restructuring without behavior change.
  • improvement — quality, DX, or polish work that isn't a bug or a new feature.
  • question — the author is asking for clarification or usage help.
  • duplicate — already tracked by another issue (link it in a comment if you apply this).
  • invalid / wontfix — only if the issue itself states this or the content clearly indicates it; otherwise skip.
  • good first issue — small, well-scoped, approachable for newcomers.
  • help wanted — maintainer explicitly wants external contribution; do not apply speculatively.
  • considering — proposals that are worth discussing but not yet accepted.
  • high priority — explicit urgency signals (regression, blocking users, security). Be conservative.
  • security — security-relevant reports or hardening work.
  • codex — specific to the Codex CLI integration.
  • maintainer-scrap — do NOT add this unless the issue body explicitly says so; it's reserved for maintainer-only scratch notes.
Show full SKILL.md (149 more words)Show less

Guidelines:

  • Prefer a small, precise set of labels (usually 1–3). Do not over-label.
  • Combine a type label (bug / enhancement / documentation / refactoring / improvement / question) with optional modifiers (good first issue, considering, security, codex) when they clearly apply.
  • If the issue is ambiguous, still apply the best-fitting type label rather than skipping it, and note the ambiguity in the final report. Skip only when the issue is empty or unreadable.

Step 5: Apply the Labels

Apply the chosen labels using gh issue edit. Example:

bash
gh issue edit <issue_number> --add-label "bug" --add-label "good first issue"

Only add labels; do not remove existing ones (these issues have none by definition, but be defensive).

Step 6: Report

Output a concise summary grouped by action:

  • Labeled: #<number> <title> → label1, label2 (one line per issue)
  • Labeled (ambiguous): #<number> <title> → label — why it was a close call
  • Skipped: #<number> <title> → short reason (empty or unreadable only)

Keep the report compact; do not repeat the full issue bodies.

© dyoshikawa, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .rulesync/skills/triage-issues of dyoshikawa/rulesync.

Open the folder on GitHubat commit 2c577d0

Compare with similar skills

Triage Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Triage Issues compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Triage Issues this skilldyoshikawa/rulesync1.5k—~896Automated safety check: PassMIT
Setup Matt Pocock Skillsbestofjs/bestofjs3.1k20 repos~1.7kAutomated safety check: PassMIT
Windows App SDK Issue Triage Reportmicrosoft/WindowsAppSDK4.7k—~3.4kAutomated safety check: PassApache-2.0
Exposed Bug Fix WorkflowJetBrains/Exposed9.3k—~3.8kAutomated safety check: PassApache-2.0
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
WinAppSDK Triage Meeting Prepmicrosoft/WindowsAppSDK4.7k—~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • Setup Matt Pocock Skills

    bestofjs/bestofjs

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.

    3.1k GitHub starsUsed in 20 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Windows App SDK Issue Triage Report

    microsoft/WindowsAppSDK

    Official

    Generates GitHub Feature Area Status reports for the Windows App SDK repository, scoring issues so teams can see what needs attention in each area.

    4.7k GitHub stars~3.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Exposed Bug Fix Workflow

    JetBrains/Exposed

    Official

    Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.

    9.3k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • WinAppSDK Triage Meeting Prep

    microsoft/WindowsAppSDK

    Official

    Prepares the triage meeting summary for WinAppSDK Needs-Triage issues, with research-backed area suggestions, draft replies and a diff since the last triage.

    4.7k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed

  • A2ui Issue Triage

    a2ui-project/a2ui

    Automates the triage of GitHub issues in the A2UI repository.

    17k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

More from dyoshikawa/rulesync

All 40 skills in this repo

  • Rulesync Feature Research

    dyoshikawa/rulesync

    Maps rulesync feature implementations to upstream coding-agent documentation.

    1.5k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Babysit Dependabot PR

    dyoshikawa/rulesync

    Babysit a Dependabot dependency-bump PR all the way to merge: verify the author is the genuine Dependabot bot, diagnose and resolve any CI failure (excluding or fixing a breaking bump when needed)…

    1.5k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Commit Push PR

    dyoshikawa/rulesync

    Commit current changes, push to remote, and create or update a pull request.

    1.5k GitHub stars~458 tokensUpdated today
    Auto-check passed

  • Git Worktree Runner

    dyoshikawa/rulesync

    Manages git worktrees using git-worktree-runner (gtr). An agent skill from dyoshikawa/rulesync.

    1.5k GitHub stars~1.3k tokensUpdated today
    Auto-check: notes

  • Goal PR

    dyoshikawa/rulesync

    Drive a pull request to a clean state and merge it: run the review-pr skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge.

    1.5k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Goal Release

    dyoshikawa/rulesync

    Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the…

    1.5k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Triage Issues

What does Triage Issues do?

Triage open GitHub issues by reviewing unlabeled ones and applying the most appropriate labels based on their content. Triage Issues is an agent skill from dyoshikawa/rulesync.

When should I use Triage Issues?

Triage Issues fits situations like: tasks that involve Issue triage.

How do I install Triage Issues in Claude Code?

Run `npx skills add dyoshikawa/rulesync --skill triage-issues -a claude-code`. Or copy the skill folder (.rulesync/skills/triage-issues in dyoshikawa/rulesync) into .claude/skills/triage-issues in your project. Claude Code loads it when a task matches its description.

How do I install Triage Issues in Codex?

Run `npx skills add dyoshikawa/rulesync --skill triage-issues -a codex`. Or copy the skill folder (.rulesync/skills/triage-issues in dyoshikawa/rulesync) into .agents/skills/triage-issues in your project. Codex loads it when a task matches its description.

Can I use Triage Issues in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dyoshikawa/rulesync --skill triage-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triage-issues, .gemini/skills/triage-issues, .github/skills/triage-issues and .opencode/skills/triage-issues in your project.

What does Triage Issues need to run?

Going by SKILL.md and its folder, Triage Issues needs the command-line tools its instructions call (gh).

Does Triage Issues access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Triage Issues safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Triage Issues use?

Triage Issues is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Triage Issues use?

About 896 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Triage Issues?

Skills that share tags, products or a category with Triage Issues: Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars), Windows App SDK Issue Triage Report (microsoft/WindowsAppSDK, 4.7k stars), Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars) and Pre-Release PR Triage (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Triage Issues?

dyoshikawa (a GitHub user) maintains it in dyoshikawa/rulesync, which has 1,508 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 9, 2026.

Source: dyoshikawa/rulesync on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.