openclaw/clawhub: README-based editorial guide

openclaw/clawhub describes itself in the README as "Skill + Plugin Registry for OpenClaw". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "README", the README says: ClawHub is the public skill registry for OpenClaw: publish, version, and search text-based agent skills (a SKILL.md plus supporting files). It's designed for fast browsing + a CLI-friendly API, with moderation hooks and vector search.. That establishes the project's stated boundary, not a production test.

The README's "What you can do with it" section gives a useful starting point for deciding whether the project fits: Rename an owned skill without breaking old links or installs.. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Publish new skill versions with changelogs + tags (including latest).. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "Local dev". The source evidence includes: bun run seed:dev waits for the local Convex deployment, runs the dev fixture seed, and refreshes global stats. The fixtures are owned by @local and are safe to rerun after fixture or schema changes.. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: bun install cp .env.local.example .env.local # edit .env.local , see CONTRIBUTING.md for local Convex values # terminal A: local Convex backend bunx convex dev # terminal B: web app (port 3000) bun run dev # detached/Codex worktree preview bun run setup:worktree bun run dev:worktree wt --yes url # seed local QA fixtures and the public corpus bun run seed:dev When the README contains no runnable command, this article does not invent one. Open its "How it works (high level)" section and confirm system dependencies, default ports, and first-run initialization before using a public server.