openclaw-ghsa-maintainer

Name: openclaw-ghsa-maintainer
Availability: InStock
Author: Arry8

Automate GHSA advisory management for OpenClaw repositories via the GHSA API.

1|Updated Mar 30, 2026

Search Tags:#vulnerability #github #patching #security-advisories #ghsa #maintainer-workflow

Ready to run

npx skills add https://github.com/Arry8/openclaw-edge --skill openclaw-ghsa-maintainer

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates GHSA advisory management for OpenClaw repositories.

Core Features & Use Cases

Guardrails enforce advisory handling: read SECURITY.md, request permission before publishing, and restrict to GHSA workflows.
Fetch advisory state and linked private fork status to validate readiness for patching.
Prepare advisory content: Markdown and JSON payloads prepared safely for API consumption.
Apply updates through the GHSA API in the correct sequence, preventing misordered fields.
Publish and verify success by re-fetching state and confirming 'published' status and accurate payloads.

Quick Start

Run the GHSA maintainer workflow to inspect, patch, and publish a repository 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 GitHub security advisory management for a repository?▼

Automating GitHub security advisory management involves fetching advisory state, preparing Markdown and JSON payloads, and applying updates through the GHSA API in the correct sequence. This process ensures patching and publishing steps execute safely end-to-end.

What is the correct sequence for patching and publishing GHSA advisories?▼

Patching GHSA advisories requires fetching the advisory state and linked private fork status first, then preparing content payloads. You apply updates through the GHSA API in the correct sequence, preventing misordered fields, and finally verify publication success.

How do I validate private fork readiness before patching a GHSA vulnerability?▼

Validating private fork readiness for a GHSA vulnerability requires fetching the advisory state and checking the linked private fork status. This confirms whether the repository environment is prepared and safe to apply security patch updates.

Can I publish GitHub security advisories via the API without misordered fields?▼

Publishing GitHub security advisories via the API safely requires preparing Markdown and JSON payloads for consumption. By applying updates in the correct sequence, you prevent misordered fields and verify success by confirming the published status.

Do I need permission before publishing a GHSA advisory to a repository?▼

Yes, safe maintainer workflows require requesting permission before publishing a GHSA advisory. Guardrails enforce reading the SECURITY.md file and restrict actions strictly to GHSA workflows to ensure secure advisory handling.