What problem does it solve? Managing GitHub Security Advisories (GHSA) for OpenClaw involves error-prone API calls, strict field sequencing rules, and private fork checks that can cause publish failures or malformed advisory content if done by hand. ## Core Features & Use Cases - Advisory Inspection: Fetch advisory state, linked private fork, and vulnerability payload shape using the GitHub API before making changes. - Safe Patching Workflow: Build Markdown descriptions via heredocs and PATCH payloads with jq, 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 verify published_at and clean description formatting. - Use Case: A maintainer needs to publish a draft GHSA for an OpenClaw vulnerability; this Skill walks through fetching the advisory, patching its fields correctly, verifying no open PRs remain on the private fork, and confirming the published state. ## Quick Start Use the openclaw-ghsa-maintainer skill to inspect and publish the draft security advisory GHSA-xxxx-yyyy-zzzz for the OpenClaw repository.