openclaw-ghsa-maintainer

Inspect, patch, validate, and publish OpenClaw GHSA advisories with gh and jq.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps security teams and developers manage GHSA advisories for OpenClaw by enabling inspection, patching, validation, and publishing while ensuring correct fork state.

Core Features & Use Cases

  • Inspect advisory state and current private fork status
  • Prepare and apply patches safely via PATCH API calls
  • Verify that private fork PRs are closed before publishing
  • Publish advisories and verify success
  • Guardrails: restricted to GHSA workflow, no general release actions

Quick Start

Run the GHSA maintainer workflow in a repository with OpenClaw advisories to begin auditing and patching.

Frequently Asked Questions about openclaw-ghsa-maintainer

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

FAQPage Schema
How do I publish GitHub security advisories safely?

To publish GitHub security advisories safely, you must first verify that all private fork PRs are closed, enforce workflow guardrails, and then execute the publish operation via the GitHub API.

What is a GHSA advisory workflow and when do I need it?

A GHSA advisory workflow is the process of inspecting, patching, validating, and publishing security advisories. You need it when managing private-fork state and applying secure patches to vulnerable repositories.

How do I check private fork state before patching a security advisory?

You can check private fork state by inspecting the advisory state and retrieving current private-fork PR status using gh and jq to ensure all PRs are closed before applying patches.

Can I use this GHSA maintainer for general GitHub release management?

No, this GHSA maintainer cannot be used for general release management. It is restricted by guardrails to the GHSA workflow only and performs no general release actions.

Why does my security advisory publish workflow fail validation?

Your security advisory publish workflow fails validation if private fork PRs remain open or if patch application via the PATCH API call encounters state conflicts during the guardrail checks.

Do I need jq and gh to manage GHSA advisories?

Yes, you need gh and jq installed because the advisory management workflow relies on these tools to handle API interactions, retrieve advisory states, and parse JSON responses safely.