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: Verifies whether a bug affects the latest shipped tag or npm release before closing, using git tags, npm version checks, and fix-commit provenance. - Trust-Model Scoping: Evaluates reports against SECURITY.md boundaries to distinguish real boundary bypasses from out-of-scope local same-user or prompt-injection findings. - Maintainer-Ready Responses: Drafts one firm, specific close or narrow comment per advisory, copies it to the clipboard, and separates optional hardening notes from closure rationale. - Use Case: A maintainer receives a new GHSA claiming a workspace-memory injection bug; the skill walks through reading the advisory, checking shipped tags, confirming the trust-model scope, and drafting a single public-safe reply. ## Quick Start Ask the assistant to triage a specific OpenClaw GHSA advisory and draft a maintainer-ready response with shipped-release evidence.