Openclaw Ghsa Maintainer
Inspect, patch, validate, publish, or confirm OpenClaw GHSA security advisories and private-fork state.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Openclaw Ghsa Maintainer when an AI agent needs a reusable SKILL.md workflow for this job: Inspect, patch, validate, publish, or confirm OpenClaw GHSA security advisories and private-fork state.
When not to use it
Skip Openclaw Ghsa Maintainer when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/openclaw-ghsa-maintainer # Save SKILL.md to ~/.claude/skills/openclaw-ghsa-maintainer/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/openclaw-ghsa-maintainer/SKILL.md. For a shared project, commit the folder at .claude/skills/openclaw-ghsa-maintainer/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Openclaw Ghsa Maintainer skill for this task: Use Openclaw Ghsa Maintainer when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
68/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 70/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# 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:
```bash 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:
```bash 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:
```bash 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:
```bash 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:
```bash 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.
Intended uses
- Use Openclaw Ghsa Maintainer when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.