security-triage

Read and triage GitHub security advisories with tag and commit verification.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Jnuso/OpenClaw --skill security-triage-jnuso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-triage
Source: https://github.com/Jnuso/OpenClaw/tree/main/.agents/skills/security-triage
Command: npx skills add https://github.com/Jnuso/OpenClaw --skill security-triage-jnuso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers quickly evaluate GitHub security advisories, drafts, and GHSA reports for OpenClaw, delivering clear, actionable close or keep decisions with verified tag/commit checks and a structured reply template.

Core Features & Use Cases

  • Guided triage workflow that reads SECURITY.md, analyzes the GHSA body via API, and inspects implicated code paths.
  • Verifies the shipped state using tags, releases, and commit references, ensuring decisions reflect the current product state.
  • Produces maintainer-ready outcomes and copy-paste replies, with optional hardening notes when appropriate.

Quick Start

To begin triaging, run the triage workflow on a new advisory and follow the close/keep guidelines.

Frequently Asked Questions about security-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage GitHub security advisories for a repository?

To triage GitHub security advisories, this Skill reads the GHSA body via API, verifies shipped state using tags and commits, and applies trust-model validation to produce a precise close or keep decision.

What is the best way to determine if a GHSA report applies to my current release?

The best way to validate a GHSA report against your release is to inspect exact code paths and verify canonical references for tags and commits, ensuring the triage decision reflects the current product state.

Can I use this triage workflow for draft security advisories and SECURITY.md references?

Yes, this triage workflow supports draft security advisories, published GHSA reports, and SECURITY.md references to evaluate vulnerabilities and generate maintainer-ready outcomes.

How do I generate a maintainer-ready reply for a security advisory report?

You generate a maintainer-ready reply by completing the guided triage workflow, which produces a structured, copy-paste response template with optional hardening notes for the security advisory.

Does this security triage process check commit status and tags before closing an advisory?

Yes, the security triage process verifies the shipped state by checking canonical references for tags, releases, and commit status before delivering a final, reply-ready close or keep decision.

Are there limitations to automated trust-model validation for security advisories?

A limitation of trust-model validation is that it relies on exact code-path inspection and canonical tag or commit checks, meaning decisions are constrained by the accuracy of the available repository references.