What problem does it solve? Managing GitHub Security Advisories (GHSA) involves fragile API constraints, private fork checks, and Markdown formatting pitfalls that can cause failed publishes or malformed advisory content. This Skill encodes the correct workflow so maintainers avoid common footguns like HTTP 422 errors and escaped newline corruption. ## Core Features & Use Cases - Advisory Inspection: Fetch advisory state, linked private fork details, and the latest published npm version before making changes. - Safe Patching Workflow: Build PATCH payloads with jq and heredoc-based Markdown files, applying severity and CVSS vector updates in separate calls as the API requires. - Publish Verification: Confirm private fork PRs are closed, publish by setting state to published, and re-fetch to validate state, published_at, and clean description formatting. - Use Case: A maintainer needs to publish a draft GHSA for a patched vulnerability. The Skill guides them through checking open PRs on the private fork, writing the advisory description safely, sequencing the PATCH calls, and verifying the published result. ## Quick Start Use the openclaw-ghsa-maintainer skill to inspect advisory GHSA-xxxx, prepare its patch payload, and publish it after verifying the private fork has no open PRs.
