Agent skill · Security

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.

SafeAI-Lab-Xgithub.com/SafeAI-Lab-XGitHub ↗
claude-code
Install
npx skills add SafeAI-Lab-X/ClawKeeper --skill openclaw-release-maintainer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 3 KB
Bundled scripts: none
Path: legacy/clawkeeper-watcher/.agents/skills/openclaw-release-maintainer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,034
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# OpenClaw Release Maintainer Use this skill for release and publish-time workflow. Keep ordinary development changes and GHSA-specific advisory work outside this skill. ## Respect release guardrails - Do not change version numbers without explicit operator approval. - Ask permission before any npm publish or release step. - Use the private maintainer release docs for the actual runbook and `docs/reference/RELEASING.md` for public policy. ## Keep release channel naming aligned - `stable`: tagged releases only, with npm dist-tag `latest` - `beta`: prerelease tags like `vYYYY.M.D-beta.N`, with npm dist-tag `beta` - Prefer `-beta.N`; do not mint new `-1` or `-2` beta suffixes - `dev`: moving head on `main` - When using a beta Git tag, publish npm with the matching beta version suffix so the plain version is not consumed or blocked ## Handle versions and release files consistently - Version locations include: - `package.json` - `apps/android/app/build.gradle.kts` - `apps/ios/Sources/Info.plist` - `apps/ios/Tests/Info.plist` - `apps/macos/Sources/OpenClaw/Resources/Info.plist` - `docs/install/updating.md` - Peekaboo Xcode project and plist version fields - “Bump version everywhere” mean

What's inside
Steps it walks through
  1. Respect release guardrails
  2. Keep release channel naming aligned
  3. Handle versions and release files consistently
  4. Build changelog-backed release notes
  5. Run publish-time validation
  6. Use the right auth flow
  7. GHSA advisory work
Commands it runs
node --import tsx scripts/release-check.ts
pnpm release:check
pnpm test:install:smoke
More from ClawKeeper
All skills →
openai-whisper-apiTranscribe audio via OpenAI Audio Transcriptions API (Whisper).Backend & APItmuxRemote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.Otheropenclaw-test-heap-leaksInvestigate `pnpm test` memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw…Testing & QAmodel-usageUse CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the…Data & Analyticsfeishu-safety-guideOne-click deployment Skill for Feishu security governance and message anti-data-leakage guide…Securityskill-creatorCreate, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when…Security
About this skill
What does the openclaw-release-maintainer skill do?

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.

How do I install it?

Run `npx skills add SafeAI-Lab-X/ClawKeeper --skill openclaw-release-maintainer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From SafeAI-Lab-X/ClawKeeper, a repository with 1,034 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.