openclaw-ghsa-maintainer

Inspect GitHub security advisories and validate private fork states.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq.

What problem does it solve?

This skill streamlines the complex, multi-step process of managing GitHub Security Advisories (GHSA) and private-fork states, reducing the risk of manual errors during sensitive security patching workflows.

Core Features & Use Cases

  • Advisory Inspection: Fetch and validate the state of security advisories and associated private forks.
  • Safe Patching: Automate the generation and application of patch payloads using structured JSON and Markdown.
  • Workflow Validation: Ensure all security guardrails, such as verifying that no open PRs exist in private forks, are met before publishing.

Quick Start

Use the openclaw-ghsa-maintainer skill to fetch the current advisory state for the specified GHSA identifier and verify that all private fork pull requests are closed.

Frequently Asked Questions about openclaw-ghsa-maintainer

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

FAQPage Schema
How do I automate GitHub security advisory patching workflows?

GitHub security advisory patching workflows can be automated by managing the lifecycle stages of inspection, patching, and publication. This reduces manual errors by using the GitHub CLI and jq to handle authenticated API interactions and structured JSON payloads.

How do I verify private fork state before publishing a security advisory?

To verify private fork state before publishing a security advisory, you must check that all security guardrails are met. This includes ensuring no open pull requests exist in the private forks associated with the advisory before proceeding to publication.

Do I need the GitHub CLI and jq to manage GHSAs?

Yes, you need the GitHub CLI and jq to manage GHSAs. These dependencies are required to perform authenticated API interactions with GitHub and to manipulate the JSON payloads used for generating and applying security patches.

What is the best way to manage GitHub security advisories at scale?

The best way to manage GitHub security advisories at scale is to automate the inspection and validation of advisory states. Ensuring compliance with security guardrails and verifying private fork conditions reduces the risk of manual errors across multiple repositories.

How does safe patching work for GitHub security advisories?

Safe patching for GitHub security advisories works by automating the generation and application of patch payloads. It uses structured JSON and Markdown within the OpenClaw repository security maintenance scope to ensure compliance with advisory guardrails.