A CLI tool that validates, tests, and dry-runs OpenClaw plugins in an isolated sandbox before publishing to ClawHub

OpenClaw's plugin ecosystem ships broken packages to production. The Brave plugin v2026.5.2 went live with only TypeScript source and no compiled dist/, crashing every gateway that installed it into an unrecoverable 1.2-second restart loop. Four separate GitHub issues filed for the same root cause. The new defineToolPlugin SDK (v2026.5.18) gives plugin authors a typed API, but there is no validation step between writing a plugin and publishing it to ClawHub where 44,000+ skills live. This tool runs a full lifecycle check in an isolated container: schema validation, build verification, dependency audit, gateway integration test, and provider registration smoke test. It catches the exact class of bugs that took down Brave search users.

Demand Breakdown

GitHub

Social Proof 4 sources

@openclaw/brave-plugin@2026.5.2 published without compiled dist/

2026-05-15

21 GH

Brave plugin install + tools.web.search.provider: 'brave' causes 1.2s crash loop with no CLI escape

2026-05-15

20 GH

5.2 brave plugin install fails with missing openclaw.extensions

2026-05-13

14 GH

web_search fails in sub-agent sessions with bundled Brave provider after v2026.4.29

2026-05-14

Gap Assessment

UnderservedExisting solutions leave gaps. Underserved market

2 tools exist (openclaw plugins validate (built-in), qa-patrol (community plugin)) but gaps remain: No build verification (doesn't check if dist/ exists), no integration test (doesn't boot a gateway), no pre-publish tarball check. Misses the entire class of 'source-only publish' bugs.; Tests agent behavior, not plugin packaging. Doesn't validate plugin build artifacts or catch provider registration failures..

Features3 agent-ready prompts

Schema and build validator that checks plugin manifest, verifies compiled dist/ exists, and catches missing exports before publish

▶

Docker-based integration test runner that boots a disposable OpenClaw gateway, installs the plugin, and verifies provider registration succeeds without crashes

▶

Pre-publish dry-run that simulates npm publish, compares the tarball contents against what the manifest declares, and blocks publish if dist/ is missing

▶

Competitive LandscapeFREE

Product	Does	Missing
openclaw plugins validate (built-in)	Basic manifest validation via the CLI. Checks JSON structure and required fields.	No build verification (doesn't check if dist/ exists), no integration test (doesn't boot a gateway), no pre-publish tarball check. Misses the entire class of 'source-only publish' bugs.
qa-patrol (community plugin)	AI-powered QA testing skill for OpenClaw. Automated browser testing with 39 bug patterns.	Tests agent behavior, not plugin packaging. Doesn't validate plugin build artifacts or catch provider registration failures.

Aggregate Score

372,141

0 leads found

Details

TypeProduct Idea

Competitors2

Features3

Issues4

Leads0

Source Signals

All signals →

372KOpenClaw v2026.5.18: defineToolPlugin Ships Typed Plugin SDK with Build/Validate/Init CLI 73OpenClaw v2026.5.18: defineToolPlugin API, Plugin Externalization (Bedrock/Slack/Vertex), Mac App Redesign 68Brave Plugin Install Puts OpenClaw Gateway Into 1.2s Crash Loop With No CLI Escape 0OpenClaw v2026.5.18 ships defineToolPlugin: typed plugin SDK with CLI tooling

Related Ideas

All ideas →

0A CLI tool that validates OpenClaw upgrades against your running configuration, channels, and plugins before you commit to the update 0A CLI tool that tests OpenClaw release upgrades against your running config, plugins, and channels before you apply them 0A CLI tool that validates your OpenClaw instance configuration and plugins against a target version, reports exactly what will break, and generates a migration patch before you upgrade