New: 97,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

Update Triage

by warpdotdev in warpdotdev/oz-for-oss

Update the repo-local triage-issue-local companion skill using signals from recently triaged issues (maintainer re-labels, re-opens, follow-up comments).

MITAuto-check passedDevelopment

Install Update Triage

skills CLI
$ npx skills add warpdotdev/oz-for-oss --skill update-triage -a claude-code

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

GitHub CLI
$ gh skill install warpdotdev/oz-for-oss update-triage --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/warpdotdev/oz-for-oss.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/update-triage .claude/skills/update-triage && 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
update-triage
GitHub stars
313
Token cost
~1k tokens
SKILL.md length
479 words
Files
2 (incl. scripts)
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

Update the repo-local triage-issue-local companion skill using signals from recently triaged issues (maintainer re-labels, re-opens, follow-up comments).

  • Works in 2 steps: Verify GitHub CLI auth → Aggregate the triage-feedback signals…
  • Refining repo-specific triage heuristics and label taxonomy based on how maintainers overrode previous triage output
  • SKILL.md covers Write surface, Inputs, Workflow and Evidence Rules, plus 1 more section
  • Runs Python scripts from its folder; calls gh, python3 and git

What it does

Update Triage is an agent skill from warpdotdev/oz-for-oss. Update the repo-local triage-issue-local companion skill using signals from recently triaged issues (maintainer re-labels, re-opens, follow-up comments). Use when refining repo-specific triage heuristics and label taxonomy based on how maintainers overrode previous triage output.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/aggregate_triage_feedback.py`).

It sits in Development, covering Issue triage. It works with GitHub. The repository describes itself as: Workflows and skills to help people and agents collaborate on open-source software with the power of Oz! The licence is MIT.

When your agent uses it

  • Refining repo-specific triage heuristics and label taxonomy based on how maintainers overrode previous triage output
  • Tasks that involve Issue triage

Example prompts

  • “/update-triage”

Requirements

  • Python 3

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Verify GitHub CLI auth
  2. Aggregate the triage-feedback signals for recently triaged issues with the bundled script

What it can do on your machine

Read from SKILL.md and the folder at commit a2bb45f. 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

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • gh
    • python3
    • git

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

  • Network

    No URLs in SKILL.md. Its commands use gh and git, 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

Update Triage loads about 1k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 479 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from warpdotdev/oz-for-oss at commit a2bb45f, republished under its MIT licence (© warpdotdev). 479 words, ~1,028 tokens.

Download SKILL.mdSave it as .claude/skills/update-triage/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
update-triage
description
Update the repo-local triage-issue-local companion skill using signals from recently triaged issues (maintainer re-labels, re-opens, follow-up comments). Use when refining repo-specific triage heuristics and label taxonomy based on how maintainers overrode previous triage output.

Update Triage

Use this skill to improve .agents/skills/triage-issue-local/SKILL.md (and, when a label taxonomy change is warranted, .github/issue-triage/config.json) from real maintainer feedback on recent triage outcomes. The core skill at .agents/skills/triage-issue/SKILL.md is the cross-repo contract and is read-only from this loop.

Closed-as-duplicate signals are handled by the separate update-dedupe loop, not here.

Write surface

This self-improvement loop may only write to:

  • .agents/skills/triage-issue-local/ (and SKILL.md inside it)
  • .github/issue-triage/*

It must NOT touch:

  • .agents/skills/triage-issue/SKILL.md (the core contract)
  • any other core skill
  • the dedupe companion .agents/skills/dedupe-issue-local/SKILL.md (owned by update-dedupe)

The self-improvement runner enforces this via a git diff check against allowed prefixes before pushing. A violation aborts the run.

Inputs

  • Optional repository override if you are not running from the target checkout.
  • Optional time window override when you need something other than the default seven-day lookback.

Workflow

  1. Verify GitHub CLI auth:
bash
gh auth status
  1. Aggregate the triage-feedback signals for recently triaged issues with the bundled script:
bash
python3 .agents/skills/update-triage/scripts/aggregate_triage_feedback.py

By default this targets the current repo and looks back 7 days. It collects issues that were triaged in the window, any subsequent maintainer re-labels, re-opens, and follow-up comments. Closed-as-duplicate events are intentionally excluded. The script writes structured JSON to a temporary file and prints the path.

  1. Read the generated JSON and look for repeated reviewer signals:
  • maintainers repeatedly flipping the same label on similar issues (a label-taxonomy hint)
  • maintainers leaving the same kind of follow-up comment on the same class of issue (a recurring follow-up-question pattern)
  • maintainers consistently identifying a different owner than Oz inferred (an owner-inference hint)
  1. Propose the smallest edit that explains the repeated signal:
  • Prefer editing .agents/skills/triage-issue-local/SKILL.md under the override categories the core triage-issue skill marks as overridable (label taxonomy, owner-inference hints, recurring follow-up-question patterns, recurring issue-shape heuristics, repro defaults, known-duplicate clusters).
  • Only edit .github/issue-triage/config.json when the signal is a concrete label-taxonomy change (new label, renamed label, or description clarification). Never change color values without explicit maintainer guidance.
  1. Keep the core triage contract stable — never edit triage-issue/SKILL.md. Only the -local companion and the triage config evolve from feedback.
Show full SKILL.md (143 more words)Show less

Evidence Rules

  • Prefer patterns backed by multiple issues or a strong explicit maintainer statement.
  • Skip the PR when there is no repeated signal. A one-off maintainer override is not enough evidence.
  • Avoid encoding reporter-authored content as triage rules.
  • Do not weaken the reserved-label rules (ready-to-implement, ready-to-spec) or the mutual exclusivity of duplicate_of and follow_up_questions.

Final Checks

  • Re-read the updated triage-issue-local companion skill and confirm any new rules are explicit.
  • Keep the companion concise; do not turn it into a long style guide.
  • Commit any changes on a local branch named oz-agent/update-triage. Do NOT push the branch; the Python entrypoint will run a write-surface guard and push only when the guard passes.
  • If the updates warrant a PR, it will be opened from the pushed branch. Tag @captainsafia as a reviewer on that PR.
  • Validate any temporary JSON with jq before relying on it.

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

Files

SKILL.md and 1 other file (scripts) in .agents/skills/update-triage of warpdotdev/oz-for-oss.

  • SKILL.md
  • scripts/aggregate_triage_feedback.py

Open the folder on GitHubat commit a2bb45f

Compare with similar skills

Update Triage 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.

Update Triage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Update Triage this skillwarpdotdev/oz-for-oss313—~1kAutomated 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 today
    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 warpdotdev/oz-for-oss

All 17 skills in this repo

  • Update Dedupe

    warpdotdev/oz-for-oss

    Update the repo-local dedupe-issue-local companion skill using closed-as-duplicate signals.

    313 GitHub stars~927 tokensUpdated 20 days ago
    Auto-check passed

  • Update PR Review

    warpdotdev/oz-for-oss

    Update the repo-local review-pr-local and review-spec-local companion skills using human feedback left on pull request conversations.

    313 GitHub stars~1.6k tokensUpdated 20 days ago
    Auto-check passed

  • Bootstrap Issue Config

    warpdotdev/oz-for-oss

    Bootstrap the issue triage configuration for a repository by analyzing existing issues, labels, and contributors to generate .github/issue-triage/config.json and .github/STAKEHOLDERS.

    313 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed

  • Implement Issue

    warpdotdev/oz-for-oss

    Implement a GitHub issue in this repository by applying the shared implement-specs workflow with Oz-specific issue, spec-context, and summary-file handling.

    313 GitHub stars~2k tokensUpdated 20 days ago
    Auto-check passed

  • Review Spec

    warpdotdev/oz-for-oss

    Review a spec/plan pull request diff and write structured feedback to review.json for the workflow to publish.

    313 GitHub stars~1.9k tokensUpdated 20 days ago
    Auto-check passed

  • Create Product Spec

    warpdotdev/oz-for-oss

    Create a product spec from a GitHub issue in this repository by applying the shared write-product-spec workflow with Oz-specific issue context and output paths.

    313 GitHub stars~1.2k tokensUpdated 20 days ago
    Auto-check passed

Works with

Categories

Questions about Update Triage

What does Update Triage do?

Update the repo-local triage-issue-local companion skill using signals from recently triaged issues (maintainer re-labels, re-opens, follow-up comments). Update Triage is an agent skill from warpdotdev/oz-for-oss. Update the repo-local triage-issue-local companion skill using signals from recently triaged issues (maintainer re-labels, re-opens, follow-up comments).

When should I use Update Triage?

Update Triage fits situations like: refining repo-specific triage heuristics and label taxonomy based on how maintainers overrode previous triage output; tasks that involve Issue triage.

How do I install Update Triage in Claude Code?

Run `npx skills add warpdotdev/oz-for-oss --skill update-triage -a claude-code`. Or copy the skill folder (.agents/skills/update-triage in warpdotdev/oz-for-oss) into .claude/skills/update-triage in your project. Claude Code loads it when a task matches its description.

How do I install Update Triage in Codex?

Run `npx skills add warpdotdev/oz-for-oss --skill update-triage -a codex`. Or copy the skill folder (.agents/skills/update-triage in warpdotdev/oz-for-oss) into .agents/skills/update-triage in your project. Codex loads it when a task matches its description.

Can I use Update Triage 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 warpdotdev/oz-for-oss --skill update-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-triage, .gemini/skills/update-triage, .github/skills/update-triage and .opencode/skills/update-triage in your project.

What does Update Triage need to run?

Going by SKILL.md and its folder, Update Triage needs Python for the scripts in its folder and the command-line tools its instructions call (gh, python3 and git). Our summary lists: Python 3.

Does Update Triage access the network?

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

Is Update Triage 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Update Triage use?

Update Triage 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 Update Triage use?

About 1k tokens (SKILL.md is roughly 4.1k 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 Update Triage?

Skills that share tags, products or a category with Update Triage: 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 Update Triage?

warpdotdev (a GitHub organization) maintains it in warpdotdev/oz-for-oss, which has 313 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on September 17, 2026.

Source: warpdotdev/oz-for-oss on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.