security-triage

Name: security-triage
Availability: InStock
Author: vut08905

Triage GitHub security advisories for OpenClaw with close/keep decisions.

Updated Apr 7, 2026

Search Tags:#security #github #verification #triage #maintainers #advisories #ghsa

Ready to run

npx skills add https://github.com/vut08905/openclaw-app --skill security-triage-vut08905

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-triage
Source: https://github.com/vut08905/openclaw-app/tree/main/.agents/skills/security-triage
Command: npx skills add https://github.com/vut08905/openclaw-app --skill security-triage-vut08905

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage GitHub security advisories for OpenClaw with structured, high-confidence close/keep decisions, exact tag/commit verification, and a ready-to-share, clipboard-friendly final reply.

Core Features & Use Cases

Structured triage guidelines: a repeatable process to classify advisories as close or keep with explicit criteria.
Proof-of-validation steps: verify shipped state via git tags, release data, and exact fix commits, referencing SECURITY.md and GHSA details.
Operator-ready output: produce a concise, paste-ready reply for maintainers to post.

Quick Start

Review a new GHSA advisory and generate a maintainer-ready triage response using the defined trust checks.

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 to decide whether to close or keep them?▼

Triage GitHub security advisories by applying structured criteria to verify shipped state using git tags, release data, and exact fix commits, cross-checking SECURITY.md and GHSA details to produce high-confidence close or keep decisions.

What is the best way to verify if a security advisory applies to my shipped release state?▼

Verifying shipped release state involves checking git tags, release data, and exact fix commits against GHSA details and SECURITY.md, ensuring the advisory classification accurately reflects the project's current vulnerability status.

How do I generate a ready-to-paste maintainer response for a GHSA report?▼

Generate a ready-to-paste maintainer response by completing verification and classification steps, which cross-check advisory details with repository data to output a concise, clipboard-friendly reply for maintainers.

Can I use automated security triage for OpenClaw advisories without manual verification?▼

Automated security triage for OpenClaw advisories requires explicit proof-of-validation steps, using git tags and commit history to verify the shipped state, ensuring high-confidence decisions rather than fully automated closure.

What criteria should I use to classify GitHub security advisories during triage?▼

Classify GitHub security advisories using structured triage guidelines that evaluate exact fix commits, release verification, and cross-checks against SECURITY.md to determine if an advisory should be closed or kept.