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

/review-security-issue

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

Review an authorized security issue or private GitHub advisory for validity, severity, and a remediation plan.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈33 tokens for metadata: the name and description. ≈544 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 ≈134 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.

Review Security Issue

Review a security concern through its authorized private workflow. Do not file or expand a vulnerability in a public issue; follow SECURITY.md. A direct request to review authorizes review only, not remediation. For unattended review, verify authorization from maintainer direction and accessible discussion; for issues, also inspect current state:* label descriptions and assignments.

Assess

  1. Fetch the requested source. For a GHSA, use gh api --method GET repos/OWNER/REPO/security-advisories/GHSA-ID and read any supplied private discussion or fix links. The advisory payload does not include its discussion; report inaccessible prior discussion as unverified. For an issue, use gh issue view <id> --json title,body,state,labels,comments and follow Label Discovery in CONTRIBUTING.md; GHSA lifecycle states are not issue labels. Verify authorization and check whether a prior review already answers the request.
  2. Check the required advisory report format and supporting reproduction or concrete code evidence. If either is missing, return a concise request for the missing sections or evidence before technical triage. Do not fill gaps with assumptions or treat scanner output as proof.
  3. Inspect affected code and verify the claim. Assess impact, exploitability, prerequisites, affected surface, and a concrete attack scenario. Separate reported claims, code inspection, and reproduced results; check the attacker's existing authority and give a severity with rationale.
  4. If actionable, propose a remediation plan with code areas, safe rollout, and focused tests. If not actionable, explain the evidence and recommended disposition. Do not decide product acceptance or silently close the issue.
  5. Post the review or revision request only when the request authorizes posting. Begin the comment with > **🔒 security-review-agent** so later reviews can detect it. Keep sensitive details in the authorized private venue.

A human decides whether to authorize remediation. Route an authorized fix to fix-security-issue. Do not introduce agent:* workflow labels.

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 warning8mo3 checks · Risk SAFE
  • Gen Agent Trust Hub8mo

    This skill is designed to review security-related GitHub issues. It uses the official GitHub CLI to read content and post reviews. The analysis confirms the skill follows security best practices, such as using quoted heredocs to prevent command injection. While it processes untrusted issue content, this is inherent to its purpose and does not present a critical risk.

  • Socket8mo

    No alerts

  • Snyk8mo

    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 4 weeks ago
metadata
{
  "internal": true
}

README badge

README badge for nvidia/openshell/review-security-issue