Agent skill · software engineering · steipete
release-openclaw-plugin-testing
Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E, Package Acceptance, and Testbox proof.
Why this skill is useful
Adds specific commands and validation procedures for OpenClaw plugin testing that the AI wouldn't reliably generate on its own.
What it needs
Requires docker, pnpm installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 385,400 stars on the source repository.
What this skill does
OpenClaw Pre-Release Plugin Testing Use this skill when the user asks for plugin release confidence, plugin lifecycle sweeps, package-artifact plugin proof, or "what else should we test before release?" It complements openclaw-testing; use that skill too when choosing the cheapest safe runner or debugging a failing lane. Goal Prove the plugin system as a product surface, not just as source tests: bundled plugin lifecycle: install, inspect, enable, disable, uninstall package artifact behavior from a clean HOME doctor/fix/config validation and idempotence config discovery and config round-trip status/log visibility and diagnostics gateway startup/bootstrap with plugin metadata snapshots public SDK compatibility for real external plugins live-ish provider/channel probes only when safe credentials exist First Checks From the OpenClaw repo root: Follow openclaw-testing for dependency ownership and the choice of local or remote proof. Runner Choice Prefer this order: 1. GitHub Package Acceptance for installable-package product proof. 2. Current dedicated Linux worker for trusted source/package/Docker proof when it has the required dependencies and capabilities. 3. ci-build-artifacts-testbox.yml Testbox when Docker/package lanes need seeded dist, dist-runtime, and package caches. 4. ci-check-testbox.yml Testbox for source checks, targeted Vitest, package-boundary checks, or focused Docker lanes. 5. Workstation targeted commands only for small format/static/unit probes. Avoid long package Docker runs from a stale sparse worktree. If Testbox sync reports hundreds of changed files or starts deleting package inputs, stop and warm a fresh box from current main, or switch to Package Acceptance. Existing Baseline Run or verify these before inventing new coverage: For full bundled install/uninstall proof, shard the packaged sweep: This example partitions the selected package's plugin inventory over shards 0-7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/release-openclaw-plugin-testing