[BREAKGLASS] Credential-free kitchen-sink OpenClaw plugin fixture covering the public plugin API surface.
Go to file
2026-04-27 10:01:06 +00:00
.github Opt actions into Node 24 runtime 2026-04-26 19:25:15 -07:00
scripts Create OpenClaw kitchen sink plugin 2026-04-26 19:24:23 -07:00
src Create OpenClaw kitchen sink plugin 2026-04-26 19:24:23 -07:00
.gitignore Create OpenClaw kitchen sink plugin 2026-04-26 19:24:23 -07:00
openclaw.plugin.json Create OpenClaw kitchen sink plugin 2026-04-26 19:24:23 -07:00
package-lock.json Update OpenClaw SDK surface to 2026.4.24 2026-04-27 10:01:06 +00:00
package.json Create OpenClaw kitchen sink plugin 2026-04-26 19:24:23 -07:00
README.md Create OpenClaw kitchen sink plugin 2026-04-26 19:24:23 -07:00

OpenClaw Kitchen Sink Plugin

Credential-free OpenClaw plugin fixture that intentionally touches the public plugin API surface.

This repo is both:

  • a readable example for plugin authors
  • a dummy compatibility fixture for Crabpot and plugin-inspector

The runtime handlers are no-op probes. They should not call external services, read secrets, spawn processes, or require live credentials.

API Surface Sync

The generated files under src/generated-* are derived from the installed openclaw package:

npm install
npm run sync:surface
npm test

When Dependabot bumps openclaw, npm test verifies that this fixture still covers every discovered hook, registrar, manifest contract key, and plugin SDK export path for that package version.

Why Generated Files Exist

Crabpot and plugin-inspector rely on static source evidence. The generated files therefore contain explicit calls such as api.registerTool(...) and api.on("before_prompt_build", ...) instead of dynamic loops.