openclaw-ghsa-maintainer

Automate GHSA advisory management from inspection to publishing.

7|12|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/borealBytes/my-farm-advisor --skill openclaw-ghsa-maintainer-borealbytes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-ghsa-maintainer
Source: https://github.com/borealBytes/my-farm-advisor/tree/main/.agents/skills/openclaw-ghsa-maintainer
Command: npx skills add https://github.com/borealBytes/my-farm-advisor --skill openclaw-ghsa-maintainer-borealbytes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates GHSA advisory management for OpenClaw, reducing manual overhead and error in security workflows.

Core Features & Use Cases

  • Inspect advisory state, fetch the latest advisory data, and verify the private fork status.
  • Build and apply patch payloads safely, ensuring sequencing and state transitions from draft to published.
  • Enforce guardrails such as no open PRs in the private fork and adherence to advisory publishing rules.

Quick Start

Run the predefined GH CLI and patch workflow commands to review, prepare, and publish an 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 GHSA advisory management and publish security advisories safely?

Automate GHSA advisory management by using workflows that inspect advisory state, verify private fork status, and apply patch payloads. Guardrails enforce sequencing and validate state transitions from draft to published using Markdown and JSON payloads.

What is the process to transition a security advisory from draft to published state?

Transitioning an advisory from draft to published involves building and applying patch payloads safely. The workflow enforces sequencing rules and validates state transitions using explicit data handling steps with Markdown and JSON payloads.

Can I publish a GHSA security advisory if there are open PRs in the private fork?

Publishing a GHSA security advisory requires no open PRs in the private fork. The workflow enforces guardrails to ensure adherence to advisory publishing rules and prevent errors during patch sequencing.

How do I verify the private fork status before applying a security advisory patch?

Verify the private fork status by inspecting the advisory state and fetching the latest advisory data. The workflow checks fork readiness before building and applying patch payloads to ensure correct state transitions.

What are the limitations of automated security advisory workflows for patch sequencing?

Automated security advisory workflows require strict adherence to publishing rules and no open PRs in the private fork. Limitations include dependency on manual validation of state transitions and ensuring correct patch payload sequencing.