openclaw-ghsa-maintainer

Manage GitHub Security Advisories by checking state, preparing patches, and publishing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured workflow to manage GitHub Security Advisories (GHSA) for OpenClaw by enforcing guardrails, ensuring private forks are clean, and guiding through patch preparation and publish steps.

Core Features & Use Cases

  • Fetch and inspect advisory state from the GHSA API to verify current status and linked private fork.
  • Verify closed PRs in the private fork before publishing to maintain security integrity.
  • Prepare advisory Markdown and JSON payloads safely using standardized tooling.
  • Apply PATCH calls in the correct sequence to update advisory state and publish.
  • Publish and verify success by re-fetching the advisory and ensuring the state is published.

Quick Start

Run the ghsa-maintainer workflow to fetch the advisory, verify the private fork and PRs, prepare the patch, and publish the advisory.

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 using the API and private forks?

Publish GitHub Security Advisories by fetching advisory states, verifying closed PRs in private forks, preparing Markdown and JSON payloads, and applying sequential PATCH calls to update and verify the published state.

What is the workflow for managing GHSA advisories end-to-end?

Managing GHSA advisories involves orchestrating advisory state checks, preparing patches safely, and executing publish actions via the GitHub API to ensure external advisories and private forks maintain security integrity throughout the process.

Do I need the gh CLI and jq to manage GitHub Security Advisories?

Yes, managing GitHub Security Advisories requires the gh CLI, jq, and GitHub API authentication to read advisory data, verify fork status, and apply PATCH updates successfully.

How do I verify a private fork before publishing a GHSA patch?

Verify a private fork before publishing by fetching advisory data from the GHSA API and checking that all associated closed PRs in the private fork are validated to maintain security integrity.

What's the best way to apply PATCH updates to GitHub Security Advisories?

The best way to apply PATCH updates to GitHub Security Advisories is using a structured workflow that prepares standardized payloads and applies API calls in the correct sequence, followed by re-fetching to verify the published state.

Why should I verify closed PRs before publishing a GitHub Security Advisory?

Verifying closed PRs before publishing a GitHub Security Advisory ensures the private fork is clean and maintains security integrity, preventing incomplete or vulnerable patch states from being publicly released.