Yuanbao Plugin Fixer

Problem it addresses

In a QClaw environment, openclaw may not be on the global PATH, and openclaw plugins install can fail because of npm dependency issues. A normal CLI install flow for the Yuanbao plugin can therefore stall on missing commands, failed dependencies, or missing or unloaded config. This skill targets plugin installation and configuration repair, specifically bypassing an unreliable install path and placing the Yuanbao plugin config where Gateway can load it.

How it works

It prefers gateway.config.patch: using valid appKey and appSecret, it writes a config fragment into ~/.qclaw/openclaw.json, then relies on Gateway hot reload instead of manual restart. If automatic config fails, it falls back to the scripts/install-plugin.sh path: download the plugin tarball, extract it into the extensions directory, install dependencies such as uuid, ws, protobufjs, and cos-nodejs-sdk-v5, then prompt for config completion. Key files include the plugin directory, openclaw.json, and the openclaw wrapper, which makes path-based debugging easier.

Boundaries and caveats

It depends on the QClaw / openclaw / Gateway local stack and is not a general plugin store. It requires valid Tencent Yuanbao Open Platform credentials. Credentials should only be written into trusted configuration and must not appear in logs, screenshots, or repositories. If the environment lacks gateway tools or paths differ, check the wrapper, plugin directory, and config file first.