OCC for OpenClaw

OCC (Origin Controlled Computing) — cryptographic proof of every OpenClaw agent action. Install, configure, and audit.

This skill appears to do what it says, but take normal precautions before installing: 1) Review the npm package source (the SKILL.md links to the GitHub repo) before running `npm install -g` — global npm installs run code on your machine. 2) If you care about privacy, use "mode": "stub" (local-only) or self-host a notary; the default uses a third-party workers.dev notary that will receive compact proof metadata (tool name, timestamp, hash, counter). 3) Note the small metadata mismatch: registry metadata said no required binaries, but the SKILL.md lists npm, npx, curl, and wrangler — make sure those tools are acceptable in your environment. 4) If you will deploy the Cloudflare Worker, ensure you understand and secure your Cloudflare account and KV namespace. 5) Prefer verifying signatures/offline verification of saved public keys before trusting remote proofs.

Type: OpenClaw Skill Name: openclaw-occ Version: 1.1.1 The skill is designed to provide cryptographic proofs of OpenClaw agent actions for auditing purposes, enhancing security and transparency. The `SKILL.md` clearly outlines its functionality, privacy considerations (e.g., what data is sent to the notary, zero-network option), and instructions for installation, configuration, and self-hosting. While it involves installing global npm packages (`npm install -g openclaw-occ`), making network calls to an external notary (`https://occ-notary.gjp9tm85hq.workers.dev/commit`), and deploying cloud resources via `wrangler`, these actions are explicitly described and aligned with the stated security-enhancing purpose. There is no evidence of prompt injection, data exfiltration beyond stated metadata, or other malicious intent within the provided files.