Plugin Integration Development

Guide users to create, validate, and integrate custom plugins, tools, and commands into OpenClaw using templates, scripts, and examples.

This skill looks like a helpful plugin template and validator, but review and test before running scripts. Specific things to check: 1) The validate script uses jq — install jq or edit the script; the skill did not declare this dependency. 2) Examples include manifest.json files, but the validator and CLI docs expect openclaw.plugin.json — update examples or manifests to match your OpenClaw version. 3) init-plugin.sh uses sed -i in a way that can be non-portable on macOS; test in a safe directory first. 4) Run the scripts in a non-production directory (or provide an explicit output-dir) to avoid accidental overwrites; the init script will refuse to proceed if the target directory exists, but confirm before running. 5) Inspect the generated index.js and manifest before installing any plugin into your real OpenClaw plugins directory. If you want higher assurance, open the scripts in a text editor or run them under a sandbox/container and verify behavior (no network calls are present).