openclaw-ghsa-maintainer

Name: openclaw-ghsa-maintainer
Availability: InStock
Author: wuv-dreamguide

Automate GHSA advisory inspection, patching, validation, and publishing workflows.

Updated Apr 21, 2026

Search Tags:#automation #security #github #maintenance #advisories #ghsa

Ready to run

npx skills add https://github.com/wuv-dreamguide/openclaw --skill openclaw-ghsa-maintainer-wuv-dreamguide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openclaw-ghsa-maintainer
Source: https://github.com/wuv-dreamguide/openclaw/tree/main/.agents/skills/openclaw-ghsa-maintainer
Command: npx skills add https://github.com/wuv-dreamguide/openclaw --skill openclaw-ghsa-maintainer-wuv-dreamguide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end GHSA advisory maintenance workflow for OpenClaw, reducing manual toil and risk when inspecting, patching, validating, and publishing advisories.

Core Features & Use Cases

Inspect advisory state from the repository’s GHSA
Build and validate Markdown and JSON payloads safely for publishing
Verify private-fork states and ensure no open PRs before publish
Publish advisories with proper sequencing, guardrails, and auditing
Confirm publish success and state updates for compliance

Quick Start

Run the ghsa-maintainer command to inspect, patch, validate, and publish a repository advisory, following guardrails.

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 maintenance for repository vulnerabilities?▼

Automating GitHub security advisory maintenance involves inspecting advisory states, patching payloads, validating private-fork constraints, and publishing with explicit confirmation. This workflow ensures API constraints are respected and reduces manual toil when managing repository GHSAs.

What is the safest way to publish GHSA advisories without causing misconfigurations?▼

Safely publishing GHSA advisories requires applying guardrails, safe payload handling, and explicit publish confirmation. You must verify private-fork states and ensure no open pull requests exist before executing the publish action to prevent unsafe misconfigurations.

How do I prepare and validate Markdown or JSON payloads for GitHub security advisories?▼

Preparing and validating Markdown or JSON payloads for GitHub security advisories requires building the content safely and checking it against API constraints. This ensures the payload formats are correct and compliant before attempting to publish the advisory.

Can I use this workflow to verify private-fork states before publishing a GHSA?▼

Yes, you can verify private-fork states before publishing a GHSA. The workflow checks private-fork states and ensures no open pull requests are present, applying necessary guardrails to prevent unsafe actions during the advisory lifecycle.

What steps are needed to inspect and patch a repository GHSA advisory?▼

Inspecting and patching a repository GHSA advisory involves running the maintainer command to check the advisory state, apply patches, validate the updated payloads, and confirm state updates for compliance before any publishing occurs.

Does GitHub advisory automation require explicit confirmation before publishing changes?▼

Yes, GitHub advisory automation requires explicit publish confirmation to prevent unsafe actions. The workflow enforces careful guardrails and safe payload handling, ensuring publish success and state updates are confirmed for compliance auditing.