security-triage

Name: security-triage
Availability: InStock
Author: pertain

Triage GitHub security advisories with verified tag and commit checks.

1|Updated Apr 10, 2026

Search Tags:#security #github #triage #response #advisories #trust-model

Ready to run

npx skills add https://github.com/pertain99/openclaw-better --skill security-triage-pertain99

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers need a consistent, high-confidence process to triage security advisories, decide between closing or keeping open, and prepare actionable replies.

Core Features & Use Cases

Structured triage criteria: define clear closure criteria (duplicates, irrelevance, or fixed in shipped releases) and keep issues open when broader verification is required.
Exact verification workflow: verify tags, commits, and implicated code paths using prescribed checks and sources.
Publish-ready replies: craft maintainer-ready responses with optional hardening notes, ready for posting or clipboard copy.

Quick Start

Begin a triage session on a new advisory and generate a maintainer-ready reply with verification notes.

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 open?▼

Triage GitHub security advisories by applying exact tag and commit verification, trust-model checks, and inspecting shipped releases to close duplicates, irrelevant issues, or fixed vulnerabilities, keeping open those needing broader verification.

What is a security advisory trust-model check for GitHub repositories?▼

A security advisory trust-model check verifies the integrity of tags and commits in a GitHub repository, ensuring that shipped releases match the implicated code paths before making a high-confidence close or keep decision.

How do I prepare a maintainer-ready reply for a GitHub security advisory?▼

Prepare a maintainer-ready reply by logging the verification workflow results, including tag and commit checks, and appending optional hardening notes to create a final response suitable for posting or copy/pasting.

Can I verify fixed vulnerabilities in shipped GitHub releases without external dependencies?▼

Yes, you can verify fixed vulnerabilities by inspecting tags, releases, and implicated code paths directly within your repository workflow, applying structured closure criteria to confirm the fix without requiring external dependencies.

When should I keep a GitHub security advisory open instead of closing it?▼

Keep a GitHub security advisory open when broader verification is required beyond standard checks, whereas you can close it confidently when the issue is a duplicate, irrelevant, or already fixed in shipped releases.