What problem does it solve? Maintainers reviewing GitHub Security Advisories (GHSA) often struggle to decide confidently whether to close or keep a report, risking either closing real vulnerabilities or shipping unnecessary regressions. This Skill provides a disciplined triage workflow that grounds every decision in shipped tags, exact commits, and the project's trust model. ## Core Features & Use Cases - High-Confidence Close/Keep Decisions: Applies a strict close bar (duplicate, invalid, out of scope, or fixed before release) so advisories are never closed just because main is fixed. - Shipped-State Verification: Verifies the exact affected state using git tags, npm release versions, and fix-commit containment checks before drafting any response. - Maintainer-Ready Replies: Produces a firm, specific close response with exact code refs, tag facts, and fix commits, then copies it to the clipboard via pbcopy. - Use Case: A maintainer receives a new GHSA claiming a boundary bypass. The Skill reads SECURITY.md, fetches the advisory via the GitHub API, checks whether the latest shipped tag is affected, and drafts a close reply citing the exact trust-model clause and release facts. ## Quick Start Triage GHSA report <GHSA-ID> for the OpenClaw repository and draft a maintainer-ready close or keep-open response.