openclaw-ghsa-maintainer

Fetch, verify, and publish GHSA advisories for OpenClaw repositories.

4|2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/bitan-del/gods-eye --skill openclaw-ghsa-maintainer-bitan-del
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-ghsa-maintainer
Source: https://github.com/bitan-del/gods-eye/tree/main/.agents/skills/openclaw-ghsa-maintainer
Command: npx skills add https://github.com/bitan-del/gods-eye --skill openclaw-ghsa-maintainer-bitan-del

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainer workflow for OpenClaw GitHub Security Advisories (GHSA) that streamlines inspection, patching, validation, and publishing of repo advisories while enforcing guardrails and safety checks.

Core Features & Use Cases

  • Fetch and inspect advisory state from GitHub GHSA endpoints and related npm versions to determine readiness.
  • Verify that the advisory's private fork has no open PRs before publish.
  • Prepare advisory payloads in Markdown and JSON safely, using shell + jq patterns and avoiding unsafe operations.
  • Apply patches and publish advisories via the GHSA API, respecting sequencing constraints and confirmation checks.

Quick Start

Execute the GitHub advisory maintainer workflow to inspect, patch, and publish a GHSA advisory for a repository while enforcing safety 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 and publishing tasks?

Automating GitHub Security Advisory maintenance involves fetching advisory state, verifying private fork PRs are closed, preparing Markdown and JSON payloads, and publishing via the GHSA API with proper sequencing and guardrails.

What is the process for verifying a GHSA advisory is ready to publish?

Verifying a GHSA advisory requires fetching advisory data from GitHub endpoints and related npm versions, then checking that the advisory's private fork has no open pull requests before proceeding to publish.

How do I safely prepare advisory payloads in Markdown and JSON formats?

Safely preparing advisory payloads uses shell and jq patterns to generate Markdown and JSON data, deliberately avoiding unsafe operations to ensure the GitHub Security Advisory output is correctly structured for publishing.

Can I use shell and jq to patch and publish GitHub Security Advisories?

Yes, you can apply patches and publish advisories via the GHSA API using shell and jq patterns, which respect sequencing constraints and enforce confirmation checks for safe repository publishing.

What safety guardrails are needed when publishing a GHSA advisory?

Publishing a GHSA advisory requires guardrails including verifying private fork PRs are closed, avoiding unsafe shell operations during payload preparation, and respecting sequencing constraints and confirmation checks via the API.