Review an authorized security issue or private GitHub advisory for validity, severity, and a remediation plan.
79%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/review-security-issue/SKILL.mdReview 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.
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.> **🔒 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.
NVIDIA/OpenShell
2e5589b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.