openclaw-ghsa-maintainer

Inspect, patch, and publish GHSA advisories with verified private-fork checks.

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

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

  • Fetch and inspect advisory state: Retrieve advisory state and the linked private fork to validate readiness.
  • Verify private fork PRs are closed: Ensure there are no open PRs in the private fork before publishing.
  • Prepare advisory Markdown and JSON safely: Build payloads using safe templating to avoid accidental escapes and injection.
  • Apply PATCH calls in correct sequence: Respect API sequencing constraints for updates to GHSA advisories.
  • Publish and verify success: Confirm the advisory state becomes published with consistent metadata.
  • Guardrails and safety: Enforce advisory-specific guardrails before any publish action.

Quick Start

Initiate the GHSA maintainer workflow to inspect an advisory, prepare payloads, and publish once all checks pass.

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 GitHub Security Advisories safely before publishing?

To manage GitHub Security Advisories safely, you must verify private fork states, assemble Markdown and JSON payloads, and enforce publish guardrails. This workflow inspects advisory readiness and applies PATCH calls in the correct sequence to prevent errors.

How do I prepare GHSA advisory payloads without causing injection vulnerabilities?

Preparing GHSA advisory payloads safely involves using safe templating to build Markdown and JSON structures. This approach prevents accidental escapes and injection vulnerabilities while assembling the required data for the GitHub API.

Do I need to check private fork PRs before publishing a GitHub Security Advisory?

Yes, you must verify that all private fork pull requests are closed before publishing a GitHub Security Advisory. This workflow checks the private fork state and ensures no open pull requests remain to satisfy API publish constraints.

What is the correct sequence for applying PATCH calls to GHSA advisories?

Applying PATCH calls to GHSA advisories correctly requires respecting API sequencing constraints during updates. This workflow orchestrates advisory state checks and patch sequencing to ensure constraints are respected before publishing.

Why does my GitHub Security Advisory publish action fail guardrails?

Your GitHub Security Advisory publish action fails guardrails because advisory-specific constraints are not met, such as open private fork pull requests or incomplete payload validation. This workflow enforces explicit guardrails before any publish action.