Appearance
Installation and Verification
Install
Install the plugin into a running OpenClaw gateway from ClawHub:
bash
openclaw plugins install clawhub:@politiclaw/politiclawOr install the package directly from npm:
bash
openclaw plugins install @politiclaw/politiclawReload the gateway (or restart the OpenClaw app) to pick up the new tools, then jump to Runtime Verification to confirm everything is wired up.
Install from source (contributors)
If you are working on the plugin in this workspace, install from a local checkout instead.
From the repository root:
bash
npm install
openclaw plugins install ./packages/politiclaw-plugin --linkThe linked install reads from the source path, so edits land without reinstalling.
Run the standard checks from the repository root:
bash
npm run build
npm run typecheck
npm run testIf you are changing docs metadata or generated reference pages, also run:
bash
npm run docs:generate
npm run docs:checkStart the VitePress app from the workspace root:
bash
npm run docs:devRuntime Verification
After the plugin is installed inside OpenClaw, use the runtime tools to verify the real environment:
- Run
/politiclaw-versionto confirm the plugin registered. - Run
/politiclaw-setupand ask your agent to callpoliticlaw_configurewith your address.politiclaw_configureis an agent tool, not a shell command. - Run
/politiclaw-doctor. - If you plan to use zero-key rep lookup,
politiclaw_configureprimes the local cache as part of rep resolution. - Fetch current reps with
politiclaw_get_my_repsif you want a direct verification pass.
What Counts As Healthy
A healthy install usually looks like this:
- The doctor tool reports working storage and a current schema version.
- Missing keys show up as actionable configuration gaps, not stack traces.
