The artifacts describe ClawHub as an OpenClaw skill/package registry and CLI, and the code supports expected user-directed actions such as search, install, update, publish, scan, and moderation workflows.

Runtime instructions and bundled skills are explicit about their scope; high-impact actions such as publishing, deleting/uninstalling, moderation, alert changes, and incident tooling are tied to user-invoked commands or documented operator workflows.

The publishable CLI package exposes a normal bin entrypoint and build-time release scripts; no hidden postinstall or automatic persistence mechanism was found in the package metadata reviewed.

The CLI uses network access, local filesystem writes, temporary files, package packing, and optional auth because those are necessary for registry, install, scan, and publish workflows; the reviewed code includes path normalization, zip path sanitization, size checks, and dry-run/confirmation paths for sensitive operations.

The CLI stores a ClawHub token in a local config file with restricted permissions and writes install lock/origin metadata under the workspace; this is disclosed and proportionate, but users should treat the token like a credential.