openclaw-ghsa-maintainer

Inspect, patch, validate, and publish GHSA advisories via gh api and jq.

1.0k|59|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/SafeAI-Lab-X/ClawKeeper --skill openclaw-ghsa-maintainer-safeai-lab-x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-ghsa-maintainer
Source: https://github.com/SafeAI-Lab-X/ClawKeeper/tree/main/legacy/clawkeeper-watcher/.agents/skills/openclaw-ghsa-maintainer
Command: npx skills add https://github.com/SafeAI-Lab-X/ClawKeeper --skill openclaw-ghsa-maintainer-safeai-lab-x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains GHSA advisories for OpenClaw by enabling inspection, patching, validation, and publishing workflows. This ensures advisories are prepared safely, with correct state tracking and compliance with GHSA APIs.

Core Features & Use Cases

  • Inspect advisory state via GHSA API and verify that any private forks have no open PRs.
  • Prepare advisory Markdown and JSON payloads safely using controlled tooling and reproducible steps.
  • Apply PATCH requests to publish advisories and verify publish success, including guardrails to prevent accidental release.
  • Use Case: When a new vulnerability is identified, generate and validate an advisory payload, confirm fork state, and publish with audit trails.

Quick Start

Open the openclaw-ghsa-maintainer skill and follow the workflow to inspect, patch, validate, and publish a GHSA 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 automate publishing GitHub security advisories using the GitHub API?

Automating GitHub security advisories involves inspecting advisory state, validating private forks, generating payloads, and applying PATCH requests via the gh api. This skill enforces guardrails to prevent accidental release and verifies publish success through audit trails.

What is the safest workflow for generating and validating GHSA payload data?

Safe GHSA payload generation requires preparing Markdown and JSON payloads using controlled tooling and reproducible steps. This skill validates private forks and ensures correct state tracking before applying any PATCH requests to publish advisories.

How do I check if a private fork has open PRs before patching a security advisory?

Checking private fork state for open PRs before patching a security advisory requires inspecting the advisory state via the GHSA API. This skill verifies fork readiness using gh api and jq to ensure safe state reconciliation.

Can I use gh api and jq to control patch application for GitHub advisories?

Using gh api and jq to control patch application for GitHub advisories provides state reconciliation and prevents accidental release. This skill enforces safe payload generation and controlled patch application under GHSA API constraints.

How to prevent accidental release when publishing GHSA advisories?

Preventing accidental release when publishing GHSA advisories requires guardrails that verify fork state, validate payloads, and confirm publish success. This skill applies controlled PATCH requests and enforces audit trails to maintain advisory integrity.

What are the limitations of automating GHSA advisory maintenance with API constraints?

Automating GHSA advisory maintenance under API constraints requires strict state reconciliation and controlled patch application to avoid errors. This skill enforces safe payload generation but is bound by GHSA API limitations for publishing and validation.