openclaw-ghsa-maintainer

Automate OpenClaw GHSA advisory governance and publishing workflows via GitHub API.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/seasonmac/Full-Scene-Agents --skill openclaw-ghsa-maintainer-seasonmac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-ghsa-maintainer
Source: https://github.com/seasonmac/Full-Scene-Agents/tree/main/openclaw/.agents/skills/openclaw-ghsa-maintainer
Command: npx skills add https://github.com/seasonmac/Full-Scene-Agents --skill openclaw-ghsa-maintainer-seasonmac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the governance and publishing workflow for OpenClaw GHSA advisories, reducing manual steps and the risk of human error.

Core Features & Use Cases

  • Fetches the current advisory state from GitHub, validates the payload format, and prepares Markdown and JSON payloads.
  • Verifies that the advisory's private fork has no open PRs before publishing.
  • Publishes the advisory via the GitHub API and confirms success, with safeguards and guardrails.

Quick Start

Inspect the advisory, patch needed changes, and publish the GHSA payload after verifying there are no open PRs in the private fork.

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 GHSA advisories via the GitHub API?

Automating GHSA advisory publishing involves querying the current advisory state via the GitHub API, generating Markdown and JSON payloads with jq, and submitting state changes in a safe sequence to reduce manual errors.

What's the best way to verify a private fork has no open PRs before publishing an advisory?

Verifying a private fork before publishing an advisory requires checking that no open pull requests exist in the fork. This guardrail ensures the advisory state is stable before submitting state changes via the GitHub API.

How does generating advisory payloads with jq work for GitHub security workflows?

Generating advisory payloads with jq works by transforming queried GitHub API advisory state data into validated Markdown and JSON formats. These payloads are then used to inspect, patch, and publish GHSA state changes safely.

Can I use this to inspect and patch OpenClaw GHSA advisories?

Yes, you can inspect and patch OpenClaw GHSA advisories by fetching the current advisory state from GitHub and applying needed changes. The workflow validates the payload format and prepares Markdown and JSON outputs for API submission.

What safeguards are in place when publishing state changes to a GHSA advisory?

Safeguards when publishing GHSA advisory state changes include verifying private fork PRs are closed, confirming payload formats, and validating API submission success. These guardrails prevent unsafe or conflicting state modifications.