openclaw-pre-release-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.
Best for Release readinessWorks with GitHubLow risk
⌘source
- author
@openclaw- language
- TypeScript
★366kstars
75kforks
Apr 29, 2026
✦overview.md
Key Features
- ·Bundled plugin lifecycle validation
- ·Package artifact behavior from clean HOME
- ·Doctor/fix/config idempotence checks
- ·Config discovery and round-trip tests
- ·Gateway startup with plugin metadata snapshots
- ·SDK compatibility for external plugins
Use Cases
- →Validating all plugins before a release
- →Testing plugin lifecycle commands end-to-end
- →Verifying package artifacts work from a fresh environment
- →Ensuring doctor/fix commands are idempotent
- →Checking SDK compatibility with real external plugins
Best for
- ✓Release readiness
- ✓Plugin system QA
- ✓CI/CD pipelines
Not ideal for
- !Unit-level plugin tests
- !Production deployments
FAQs
name
openclaw-pre-release-plugin-testing
description
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.
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:
pnpm docs:list
git status --short --branch
readlink node_modules
pnpm changed:lanes --json
In Codex worktrees under .codex/worktrees, node_modules must be a symlink to
the main OpenClaw checkout. Do not run pnpm install there. For broad or
$install
1-click copynpx skills add openclaw/openclaw --skill openclaw-pre-release-plugin-testingSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.