Index of every page on this site: llms.txt
All skills
nvidia avatar

/triage-issue

@c24fcd2
by NVIDIA Corporationnvidia/openshell22k stars
2,144
Run it yourself

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

Use this Skill: https://skilld.dev/gh/nvidia/openshell/triage-issue

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈34 tokens for metadata: the name and description. ≈882 when used: this file.

Description uses 1.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈138 characters, or 1.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Follow Labeling and Notifications: defer area/topic classification labels until the work is accepted. They drive subscriber notifications, so technical classification alone must not send unaccepted intake to those streams. Continue to record appropriate triage state.

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. Keep this assessment judgment and comment in triage.
  7. Use /label-issue to reconcile labels. Pass the assessment outcome and reviewed label subset through its assessment-only path. For accepted work, request classification when needed.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning6mo3 checks · Risk SAFE
  • Gen Agent Trust Hub6mo

    This skill automates the triaging of GitHub issues for the OpenShell project. It processes issue data, validates reporter diagnostics, and uses a sub-agent to classify reports. While it processes untrusted input from issue bodies, the behavior is consistent with its intended purpose and includes instructions for skeptical evaluation to mitigate prompt injection risks. No malicious behavior or data exfiltration patterns were detected.

  • Socket6mo

    No alerts

  • Snyk6mo

    Risk: MEDIUM · 1 issue

Signed by skilld at c24fcd2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last week
metadata
{
  "internal": true
}

README badge

README badge for nvidia/openshell/triage-issue