Agent skill

security-triage

Triage GitHub security advisories for OpenClaw with high-confidence close/keep decisions, exact tag and commit verification, trust-model checks, optional hardening notes, and a final reply ready to post and copy to clipboard.

Stars 355,710
Forks 72,004

Install this agent skill to your Project

npx add-skill https://github.com/openclaw/openclaw/tree/main/.agents/skills/security-triage

SKILL.md

Security Triage

Use when reviewing OpenClaw security advisories, drafts, or GHSA reports.

Goal: high-confidence maintainers' triage without over-closing real issues or shipping unnecessary regressions.

Close Bar

Close only if one of these is true:

  • duplicate of an existing advisory or fixed issue
  • invalid against shipped behavior
  • out of scope under SECURITY.md
  • fixed before any affected release/tag

Do not close only because main is fixed. If latest shipped tag or npm release is affected, keep it open until released or published with the right status.

Required Reads

Before answering:

  1. Read SECURITY.md.
  2. Read the GHSA body with gh api /repos/openclaw/openclaw/security-advisories/<GHSA>.
  3. Inspect the exact implicated code paths.
  4. Verify shipped state:
    • git tag --sort=-creatordate | head
    • npm view openclaw version --userconfig "$(mktemp)"
    • git tag --contains <fix-commit>
    • if needed: git show <tag>:path/to/file
  5. Search for canonical overlap:
    • existing published GHSAs
    • older fixed bugs
    • same trust-model class already covered in SECURITY.md

Review Method

For each advisory, decide:

  • close
  • keep open
  • keep open but narrow

Check in this order:

  1. Trust model
    • Is the prerequisite already inside trusted host/local/plugin/operator state?
    • Does SECURITY.md explicitly call this class out as out of scope or hardening-only?
  2. Shipped behavior
    • Is the bug present in the latest shipped tag or npm release?
    • Was it fixed before release?
  3. Exploit path
    • Does the report show a real boundary bypass, not just prompt injection, local same-user control, or helper-level semantics?
  4. Functional tradeoff
    • If a hardening change would reduce intended user functionality, call that out before proposing it.
    • Prefer fixes that preserve user workflows over deny-by-default regressions unless the boundary demands it.

Response Format

When preparing a maintainer-ready close reply:

  1. Print the GHSA URL first.
  2. Then draft a detailed response the maintainer can post.
  3. Include:
    • exact reason for close
    • exact code refs
    • exact shipped tag / release facts
    • exact fix commit or canonical duplicate GHSA when applicable
    • optional hardening note only if worthwhile and functionality-preserving

Keep tone firm, specific, non-defensive.

Clipboard Step

After drafting the final post body, copy it:

bash
pbcopy <<'EOF'
<final response>
EOF

Tell the user that the clipboard now contains the proposed response.

Useful Commands

bash
gh api /repos/openclaw/openclaw/security-advisories/<GHSA>
gh api /repos/openclaw/openclaw/security-advisories --paginate
git tag --sort=-creatordate | head -n 20
npm view openclaw version --userconfig "$(mktemp)"
git tag --contains <commit>
git show <tag>:<path>
gh search issues --repo openclaw/openclaw --match title,body,comments -- "<terms>"
gh search prs --repo openclaw/openclaw --match title,body,comments -- "<terms>"

Decision Notes

  • “fixed on main, unreleased” is usually not a close.
  • “needs attacker-controlled trusted local state first” is usually out of scope.
  • “same-host same-user process can already read/write local state” is usually out of scope.
  • “helper function behaves differently than documented config semantics” is usually invalid.
  • If only the severity is wrong but the bug is real, keep it open and narrow the impact in the reply.

Expand your agent's capabilities with these related and highly-rated skills.

openclaw/openclaw

openclaw-test-heap-leaks

Investigate `pnpm test` memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw using the `scripts/test-parallel.mjs` heap snapshot tooling. Use when Codex needs to reproduce test-lane memory growth, collect repeated `.heapsnapshot` files, compare snapshots from the same worker PID, distinguish transformed-module retention from real data leaks, and fix or reduce the impact by patching cleanup logic or isolating hotspot tests.

355,710 72,004
Explore
openclaw/openclaw

parallels-discord-roundtrip

Run the macOS Parallels smoke harness with Discord end-to-end roundtrip verification, including guest send, host verification, host reply, and guest readback.

355,710 72,004
Explore
openclaw/openclaw

openclaw-release-maintainer

Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.

355,710 72,004
Explore
openclaw/openclaw

openclaw-ghsa-maintainer

Maintainer workflow for OpenClaw GitHub Security Advisories (GHSA). Use when Codex needs to inspect, patch, validate, or publish a repo advisory, verify private-fork state, prepare advisory Markdown or JSON payloads safely, handle GHSA API-specific publish constraints, or confirm advisory publish success.

355,710 72,004
Explore
openclaw/openclaw

openclaw-pr-maintainer

Maintainer workflow for reviewing, triaging, preparing, closing, or landing OpenClaw pull requests and related issues. Use when Codex needs to validate bug-fix claims, search for related issues or PRs, apply or recommend close/reason labels, prepare GitHub comments safely, check review-thread follow-up, or perform maintainer-style PR decision making before merge or closure.

355,710 72,004
Explore
openclaw/openclaw

openclaw-parallels-smoke

End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.

355,710 72,004
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results