$ ~/registry/skill/openclaw-agents-skills-openclaw-ghsa-maintainer

SKILL

openclaw-ghsa-maintainer

Name: openclaw-ghsa-maintainer
Author: openclaw

Inspect, patch, validate, and publish OpenClaw GHSA advisories securely.

Stars

★ 382,582

Source

GitHub

Updated

2026-07-11

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 377.5k

Summary

The material indicates this is essentially prompt/documentation for the OpenClaw GHSA workflow, with no declared secrets, remote endpoints, or local data access requirements. Given the open-source source and very high community adoption, overall risk is low, though the documented examples reference GitHub/GHSA and npm commands and should still be kept within the stated scope.

CredentialsLow risk

The material explicitly states that no keys or environment variables are required. The README only describes GHSA workflow steps and does not ask for extra tokens or credential export. If gh commands are actually run, authentication would rely on the host's existing GitHub session, but the skill material itself does not directly request or expose credentials.

Network egressLow risk

The system flags it as prompt-only and no remote endpoint is declared. Although the README includes example calls to the GitHub API and npm view, these appear as instructional command patterns; based on the material itself, there is no evidence of built-in exfiltration to unknown or unrelated third-party endpoints.

Code executionLow risk

As a prompt-only skill, the material itself contains no executable program, installer, or auto-run logic. The README shows example commands using gh, jq, npm, and rg, but these are operational instructions for a human or external tool and do not mean the skill itself gains local code execution privileges.

Data accessLow risk

No built-in ability to read or write local files, repository contents, or system resources is declared. The README only mentions example practices such as writing temporary Markdown/JSON files under /tmp and inspecting GHSA responses; from the skill material alone, there is no factual basis for claiming excessive data access.

Supply chainLow risk

The source is an open-source GitHub repository with extremely high community adoption (about 377k stars), which is a strong positive trust signal. The license and maintenance status are not clearly stated, leaving a minor information gap, but there are no concrete red flags such as closed source, abandoned provenance, impersonation, or suspicious installation chains, so supply-chain risk remains low.

Recommendations

Use it only for the GHSA advisory workflow described in the documentation, not for unrelated release or system administration tasks.
If used with an execution-capable agent, restrict accessible repositories, network targets, and GitHub permission scope first.
Manually review the example commands in the README, especially PATCH/publish steps, to avoid accidental publication or changes to the wrong target.
Further verify the repository license, recent maintenance activity, and SECURITY.md content to complete compliance and operational review.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "openclaw-ghsa-maintainer" skill from askskill:
1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/openclaw-ghsa-maintainer/SKILL.md
2. Save it as ~/.claude/skills/openclaw-ghsa-maintainer/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Check advisory status

Prompt

Check the status of all current OpenClaw GHSA security advisories. List items pending patching, validation, or publication, and confirm whether the private fork is configured correctly.

Expected

A status report showing each advisory stage, risks, and private-fork configuration results.

Validate a security fix

Prompt

For this OpenClaw GHSA advisory, validate whether the patch has been applied correctly. Include reproduction steps, validation results, and whether it is ready for publication.

Expected

A validation report stating whether the issue is fixed, test conclusions, and recommended next steps.

Prepare advisory publication

Prompt

Based on the confirmed fix, create a pre-publication checklist for an OpenClaw GHSA advisory, including affected versions, fix notes, release timing, and private-fork sync confirmation.

Expected

An actionable pre-publication checklist to help maintainers release the advisory safely.

// docs

OpenClaw GHSA Maintainer

Use this skill for repo security advisory workflow only. Keep general release work in release-openclaw-maintainer.

Respect advisory guardrails

Before reviewing or publishing a repo advisory, read SECURITY.md.
Ask permission before any publish action.
Treat this skill as GHSA-only. Do not use it for stable or beta release work.

Fetch and inspect advisory state

Fetch the current advisory and the latest published npm version:

gh api /repos/openclaw/openclaw/security-advisories/<GHSA>
npm view openclaw version --userconfig "$(mktemp)"

Use the fetch output to confirm the advisory state, linked private fork, and vulnerability payload shape before patching.

Verify private fork PRs are closed

Before publishing, verify that the advisory's private fork has no open PRs:

fork=$(gh api /repos/openclaw/openclaw/security-advisories/<GHSA> | jq -r .private_fork.full_name)
gh pr list -R "$fork" --state open

The PR list must be empty before publish.

Prepare advisory Markdown and JSON safely

Write advisory Markdown via heredoc to a temp file. Do not use escaped \n strings.
Build PATCH payload JSON with jq, not hand-escaped shell JSON.

Example pattern:

cat > /tmp/ghsa.desc.md <<'EOF'
<markdown description>
EOF

jq -n --rawfile desc /tmp/ghsa.desc.md \
  '{summary,severity,description:$desc,vulnerabilities:[...]}' \
  > /tmp/ghsa.patch.json

Apply PATCH calls in the correct sequence

Do not set severity and cvss_vector_string in the same PATCH call.
Use separate calls when the advisory requires both fields.
Publish by PATCHing the advisory and setting "state":"published". There is no separate /publish endpoint.

Example shape:

gh api -X PATCH /repos/openclaw/openclaw/security-advisories/<GHSA> \
  --input /tmp/ghsa.patch.json

Publish and verify success

After publish, re-fetch the advisory and confirm:

state=published
published_at is set
the description does not contain literal escaped \\n

Verification pattern:

gh api /repos/openclaw/openclaw/security-advisories/<GHSA>
jq -r .description < /tmp/ghsa.refetch.json | rg '\\\\n'

Common GHSA footguns

Publishing fails with HTTP 422 if required fields are missing or the private fork still has open PRs.
A payload that looks correct in shell can still be wrong if Markdown was assembled with escaped newline strings.
Advisory PATCH sequencing matters; separate field updates when GHSA API constraints require it.
Public hardening/no-publish comments and draft text should avoid raw commit hashes, PR titles/numbers, and fix-mechanism summaries. Prefer patched-version fields or release-only wording; keep SHAs, PRs, and implementation notes in internal evidence.

Run, debug, monitor, and summarize OpenClaw release CI workflows.

openclawGet→

$ loading_

Please install the "openclaw-ghsa-maintainer" skill from askskill: 1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/openclaw-ghsa-maintainer/SKILL.md 2. Save it as ~/.claude/skills/openclaw-ghsa-maintainer/SKILL.md 3. Reload skills and tell me it's ready

// examples

Check advisory status

Prompt

Check the status of all current OpenClaw GHSA security advisories. List items pending patching, validation, or publication, and confirm whether the private fork is configured correctly.

Expected

A status report showing each advisory stage, risks, and private-fork configuration results.

Validate a security fix

Prompt

For this OpenClaw GHSA advisory, validate whether the patch has been applied correctly. Include reproduction steps, validation results, and whether it is ready for publication.

Expected

A validation report stating whether the issue is fixed, test conclusions, and recommended next steps.

Prepare advisory publication

Prompt

Based on the confirmed fix, create a pre-publication checklist for an OpenClaw GHSA advisory, including affected versions, fix notes, release timing, and private-fork sync confirmation.

Expected

An actionable pre-publication checklist to help maintainers release the advisory safely.

// docs

OpenClaw GHSA Maintainer

Use this skill for repo security advisory workflow only. Keep general release work in release-openclaw-maintainer.

Respect advisory guardrails

Before reviewing or publishing a repo advisory, read SECURITY.md.
Ask permission before any publish action.
Treat this skill as GHSA-only. Do not use it for stable or beta release work.

Fetch and inspect advisory state

Fetch the current advisory and the latest published npm version:

gh api /repos/openclaw/openclaw/security-advisories/<GHSA>
npm view openclaw version --userconfig "$(mktemp)"

Use the fetch output to confirm the advisory state, linked private fork, and vulnerability payload shape before patching.

Verify private fork PRs are closed

Before publishing, verify that the advisory's private fork has no open PRs:

fork=$(gh api /repos/openclaw/openclaw/security-advisories/<GHSA> | jq -r .private_fork.full_name)
gh pr list -R "$fork" --state open

The PR list must be empty before publish.

Prepare advisory Markdown and JSON safely

Write advisory Markdown via heredoc to a temp file. Do not use escaped \n strings.
Build PATCH payload JSON with jq, not hand-escaped shell JSON.

Example pattern:

cat > /tmp/ghsa.desc.md <<'EOF'
<markdown description>
EOF

jq -n --rawfile desc /tmp/ghsa.desc.md \
  '{summary,severity,description:$desc,vulnerabilities:[...]}' \
  > /tmp/ghsa.patch.json

Apply PATCH calls in the correct sequence

Do not set severity and cvss_vector_string in the same PATCH call.
Use separate calls when the advisory requires both fields.
Publish by PATCHing the advisory and setting "state":"published". There is no separate /publish endpoint.

Example shape:

gh api -X PATCH /repos/openclaw/openclaw/security-advisories/<GHSA> \
  --input /tmp/ghsa.patch.json

Publish and verify success

After publish, re-fetch the advisory and confirm:

state=published
published_at is set
the description does not contain literal escaped \\n

Verification pattern:

gh api /repos/openclaw/openclaw/security-advisories/<GHSA>
jq -r .description < /tmp/ghsa.refetch.json | rg '\\\\n'

Common GHSA footguns

Publishing fails with HTTP 422 if required fields are missing or the private fork still has open PRs.
A payload that looks correct in shell can still be wrong if Markdown was assembled with escaped newline strings.
Advisory PATCH sequencing matters; separate field updates when GHSA API constraints require it.
Public hardening/no-publish comments and draft text should avoid raw commit hashes, PR titles/numbers, and fix-mechanism summaries. Prefer patched-version fields or release-only wording; keep SHAs, PRs, and implementation notes in internal evidence.