openclaw-ghsa-maintainer

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

Automates reviewing, patching, validating and publishing GitHub Security Advisories for Argentum.

2|Updated Mar 15, 2026

Search Tags:#automation #github-api #security-advisories #ghsa #maintainer-workflow #payload-generation

Ready to run

npx skills add https://github.com/AG064/argentum --skill openclaw-ghsa-maintainer-ag064

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainer workflow for Argentum GHSA advisories ensures secure, traceable, and compliant handling of security advisories from inspection to publication.

Core Features & Use Cases

Fetch advisory state and linked fork status to determine readiness for patching and publish.
Validate and assemble advisory Markdown and JSON payloads safely, ensuring API constraints are respected.
Enforce guardrails: require advisory review, close private-fork PRs before publish, and provide audit-ready artifacts.

Quick Start

Invoke this skill to prepare advisory payloads and publish a GHSA that meets policy requirements.

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 Advisories management end-to-end?▼

You can automate GitHub Security Advisories workflows by applying a structured process that reviews, patches, validates, and publishes advisories while safely assembling Markdown and JSON payloads and sequencing API PATCH calls.

How do I generate safe Markdown and JSON payloads for GHSA publishing?▼

To generate safe GHSA Markdown and JSON payloads, validate and assemble the advisory content while respecting GitHub API constraints, using tooling like gh CLI and jq to ensure security guardrails are met.

Do I need to close private-fork PRs before publishing a GHSA advisory?▼

Yes, closing private-fork PRs before publishing a GHSA advisory is a required guardrail to verify the linked fork state and ensure a secure, traceable publication process.

Can I use gh CLI and jq to validate GitHub Security Advisory patch sequences?▼

Yes, using gh CLI and jq to validate GitHub Security Advisory patch sequences ensures reproducible updates and API constraint compliance, while enforcing guardrails and generating audit-ready artifacts.

What are the limitations of publishing GHSA advisories without verifying private fork state?▼

Publishing GHSA advisories without verifying private fork state bypasses critical security guardrails, risking unresolved merge conflicts and non-compliant patch sequences, which fails the audit-ready artifact requirement.