What problem does it solve? Maintainers reviewing GitHub Security Advisories (GHSA) risk over-closing real vulnerabilities or shipping unnecessary regressions without a consistent, evidence-based triage process tied to shipped releases and the documented trust model. ## Core Features & Use Cases - Evidence-Based Close Decisions: Applies a strict close bar covering duplicates, invalid reports, out-of-scope trust-model cases, and pre-release fixes, verified against shipped tags and npm releases. - Trust-Model Review Method: Checks each advisory against SECURITY.md scope, shipped behavior, exploit paths, and functional tradeoffs before recommending close, keep open, or narrow. - Maintainer-Ready Responses: Drafts one detailed close comment per advisory with exact code refs, release facts, and optional hardening notes, then copies it to the clipboard for posting. - Use Case: A maintainer receives a new GHSA claiming a workspace memory injection bug. The Skill walks through reading the advisory via the GitHub API, verifying whether the latest shipped tag is affected, checking the SECURITY.md trust boundary, and drafting a firm, specific close or keep-open reply. ## Quick Start Ask the assistant to triage a specific OpenClaw GHSA advisory by its ID and draft a maintainer-ready response with shipped-tag evidence.