openclaw-ghsa-maintainer

Inspect, patch, validate, and publish GHSA advisories for OpenClaw repositories.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/pertain99/openclaw-better --skill openclaw-ghsa-maintainer-pertain99
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-ghsa-maintainer
Source: https://github.com/pertain99/openclaw-better/tree/main/.agents/skills/openclaw-ghsa-maintainer
Command: npx skills add https://github.com/pertain99/openclaw-better --skill openclaw-ghsa-maintainer-pertain99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainer workflow for OpenClaw GitHub Security Advisories (GHSA). Use when Codex needs to inspect, patch, validate, or publish a repo advisory, verify private-fork state, prepare advisory Markdown or JSON payloads safely, handle GHSA API-specific publish constraints, or confirm advisory publish success.

Core Features & Use Cases

  • Inspect GHSA advisories across a repository and draft patches that address the identified vulnerability.
  • Validate advisory payloads (Markdown and JSON) and ensure private forks have no open PRs before publish.
  • Enforce guardrails and API constraints to safely prepare and publish advisories to GitHub.

Quick Start

Inspect a repository's GHSA advisory, generate the patch payload, validate it, and publish when ready.

Frequently Asked Questions about openclaw-ghsa-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage GHSA advisories end-to-end for a repository?

Managing GHSA advisories involves orchestrating inspection, patch generation, payload validation, and publish actions. This workflow ensures advisory state verification, structured payload creation, and safe publish sequencing with explicit pre-publish checks.

What guardrails are needed to safely publish GitHub Security Advisories?

Safely publishing GitHub Security Advisories requires enforcing API payload constraints and verifying private forks have no open PRs. These guardrails ensure compliant, safe releases and confirm advisory publish success.

How do I validate advisory Markdown and JSON payloads before publishing to GitHub?

Validating advisory payloads involves checking both Markdown and JSON structures against GHSA API constraints. This ensures the structured payload creation meets GitHub's requirements before proceeding with the publish sequence.

Do I need to verify private fork state before publishing a GHSA advisory?

Yes, verifying private fork state is required before publishing a GHSA advisory. You must ensure private forks have no open PRs to maintain compliant and safe releases during the advisory workflow.

Can I generate patches for identified vulnerabilities in GHSA advisories?

Yes, you can inspect GHSA advisories across a repository and generate patch payloads that address the identified vulnerabilities. This handles private forks and API constraints for safe advisory releases.