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

Official agent skill

Triage Issue

by NVIDIA in NVIDIA/OpenShell

Assess community issues, validate technical claims, request missing evidence, and prepare valid work for human disposition.

OfficialApache-2.0Auto-check passedDevelopment

Install Triage Issue

skills CLI
$ npx skills add NVIDIA/OpenShell --skill triage-issue -a claude-code

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

GitHub CLI
$ gh skill install NVIDIA/OpenShell triage-issue --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/NVIDIA/OpenShell.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/triage-issue .claude/skills/triage-issue && 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-issue
GitHub stars
15k
Token cost
~846 tokens
SKILL.md length
448 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
Apache-2.0

At a glance

Assess community issues, validate technical claims, request missing evidence, and prepare valid work for human disposition.

  • Works in 6 steps: Run gh issue view --json… → Confirm the User Story attests that the… → For bugs, verify reproduction steps… → …
  • Tasks that involve Issue triage
  • SKILL.md covers Scope and authorization and Assess one issue
  • Calls gh

What it does

Triage Issue is an agent skill from NVIDIA/OpenShell, published by the product's own GitHub organization. Assess community issues, validate technical claims, request missing evidence, and prepare valid work for human disposition.

Its SKILL.md is about 850 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. The repository describes itself as: OpenShell is the safe, private runtime for autonomous AI agents. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Issue triage

Example prompts

  • “/triage-issue”

Workflow steps

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

  1. Run gh issue view --json number,title,body,state,labels,author,comments. Follow Label Discovery in CONTRIBUTING.md to retrieve every page…
  2. Confirm the User Story attests that the human operator personally uses OpenShell and directly encountered the problem or needs the feature…
  3. For bugs, verify reproduction steps using only OpenShell deployments. Do not install third-party tools solely to demonstrate…
  4. For proposed configuration, CLI, SDK, or other UX changes, request notional examples of the suggested interaction if missing. Keep the…
  5. Reproduce or investigate enough to distinguish a confirmed bug, feasible feature, missing evidence, duplicate, already-fixed behavior, or…
  6. Post a concise comment beginning with > 📋 triage-agent. Explain the evidence, any exact missing information, and the next human decision…

What it can do on your machine

Read from SKILL.md and the folder at commit 834b79a. 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 Issue loads about 846 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 448 words of instructions outside code blocks.

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

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 NVIDIA/OpenShell at commit 834b79a, republished under its Apache-2.0 licence (© NVIDIA). 448 words, ~846 tokens.

Download SKILL.mdSave it as .claude/skills/triage-issue/SKILL.md (or your agent's skills folder).
name
triage-issue
description
Assess community issues, validate technical claims, request missing evidence, and prepare valid work for human disposition.
metadata.internal
true

Triage Issue

Triage establishes whether a reported OpenShell problem is technically valid and sufficiently evidenced. A maintainer decides whether the project accepts valid work and where it belongs on the roadmap. Inspect current GitHub label names and descriptions; the general issue lifecycle uses state:* labels, but their exact names may change.

Scope and authorization

For a specific issue, assess it when requested. For batch triage, first show the issue count and a sample of titles and obtain explicit authorization before posting comments or changing labels on multiple issues. Do not infer that a label alone authorizes bulk changes.

Do not apply an acceptance state, place issues on the roadmap, or make a product investment decision. Do not introduce agent:* workflow labels. Follow SECURITY.md if the report may disclose a vulnerability; do not copy sensitive details into a public comment.

Assess one issue

  1. Run gh issue view <id> --json number,title,body,state,labels,author,comments. Follow Label Discovery in CONTRIBUTING.md to retrieve every page of current state:* label definitions and resolve unclear meanings. Check for previous triage, new human evidence, an existing owner, and duplicate issues.
  2. Confirm the User Story attests that the human operator personally uses OpenShell and directly encountered the problem or needs the feature for a specific use case. If this is absent, request that first-hand context; do not invent it. Check the Problem Statement, impact, workaround and its limits, and observable acceptance criteria.
  3. For bugs, verify reproduction steps using only OpenShell deployments. Do not install third-party tools solely to demonstrate reproducibility. Check the OpenShell version and relevant deployment details. For features, check the user-facing workflow and alternatives. Consider applicable middleware, interceptors, providers, and other extension points; prefer an applicable extension when it satisfies the use case, and do not dismiss it merely because it runs another service.
  4. For proposed configuration, CLI, SDK, or other UX changes, request notional examples of the suggested interaction if missing. Keep the issue framed entirely in terms of OpenShell.
  5. Reproduce or investigate enough to distinguish a confirmed bug, feasible feature, missing evidence, duplicate, already-fixed behavior, or expected behavior. State what was observed and what remains uncertain. Do not turn a failed reproduction attempt alone into a dismissal.
  6. Post a concise comment beginning with > **📋 triage-agent**. Explain the evidence, any exact missing information, and the next human decision. Replace the previous assessment state with the appropriate current assessment state only after checking repository definitions. Preserve maintainer acceptance, execution state, roadmap decisions, and unrelated labels; do not accumulate assessment states.
Show full SKILL.md (32 more words)Show less

If substantial technical uncertainty remains, recommend create-spike with specific questions to answer. A direct user request can separately authorize planning or implementation through build-from-issue; it does not change the issue's recorded disposition.

© NVIDIA, Apache-2.0. 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 .agents/skills/triage-issue of NVIDIA/OpenShell.

Open the folder on GitHubat commit 834b79a

Compare with similar skills

Triage Issue 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 Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Triage Issue this skillNVIDIA/OpenShell15k—~846Automated safety check: PassApache-2.0
Setup Matt Pocock Skillsbestofjs/bestofjs3.1k20 repos~1.7kAutomated safety check: PassMIT
Wayfinderbestofjs/bestofjs3.1k20 repos~2.9kAutomated 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
Archify Reviewtt-a1i/archify79k—~415Automated safety check: PassMIT

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

  • Wayfinder

    bestofjs/bestofjs

    Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

    3.1k GitHub starsUsed in 20 repos~2.9k 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 yesterday
    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 yesterday
    DevelopmentAuto-check passed

  • Archify Review

    tt-a1i/archify

    Review Archify issues, PRs, or code through value, cost, and impact to support evidence-based maintenance decisions. Use for issue triage, change reviews, and…

    79k GitHub stars~415 tokensUpdated today
    DevelopmentAuto-check passed

  • Bug Triage

    symfony/symfony

    Decide whether open Bug PRs target the correct branch. An agent skill from symfony/symfony.

    31k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

More from NVIDIA/OpenShell

All 23 skills in this repo

  • Build Openshell Mxc Windows

    NVIDIA/OpenShell

    Official

    Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64.

    15k GitHub stars~4.9k tokensUpdated today
    Auto-check passed

  • Create GitHub Issue

    NVIDIA/OpenShell

    Official

    Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.

    15k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Create GitHub PR

    NVIDIA/OpenShell

    Official

    Create GitHub pull requests using the gh CLI. An agent skill from NVIDIA/OpenShell.

    15k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Debug Inference

    NVIDIA/OpenShell

    Official

    Debug inference clients that use an attached provider and its native endpoint, including hosted APIs and host-local Ollama, vLLM, SGLang, TRT-LLM, LM Studio, or NIM.

    15k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Debug Openshell Cluster

    NVIDIA/OpenShell

    Official

    Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes.

    15k GitHub stars~19k tokensUpdated today
    Auto-check: notes

  • Gator Gate

    NVIDIA/OpenShell

    Official

    Validate and monitor OpenShell GitHub issues and PRs using the gator: state machine.

    15k GitHub stars~19k tokensUpdated today
    Auto-check passed

Categories

Questions about Triage Issue

What does Triage Issue do?

Assess community issues, validate technical claims, request missing evidence, and prepare valid work for human disposition. Triage Issue is an agent skill from NVIDIA/OpenShell, published by the product's own GitHub organization. Assess community issues, validate technical claims, request missing evidence, and prepare valid work for human disposition.

When should I use Triage Issue?

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

How do I install Triage Issue in Claude Code?

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

How do I install Triage Issue in Codex?

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

Can I use Triage Issue 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 NVIDIA/OpenShell --skill triage-issue -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-issue, .gemini/skills/triage-issue, .github/skills/triage-issue and .opencode/skills/triage-issue in your project.

What does Triage Issue need to run?

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

Does Triage Issue 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 Issue 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 Issue use?

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

How many tokens does Triage Issue use?

About 846 tokens (SKILL.md is roughly 3.4k 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 Issue?

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

Who maintains Triage Issue?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/OpenShell, which has 15,188 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 7, 2026.

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