Clawhub Moderation
Use for ClawHub staff moderation actions with the repo-local ClawHub admin tool...
Install
npx skills add openclaw/clawhub --skill clawhub-moderation -g -a claude-code -y- Repository
- openclaw/clawhub9.5k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,113 tokens
- Runs scripts
- No, instructions only
What it does
Use for ClawHub staff moderation actions with the repo-local ClawHub admin tool: skills, users, org publishers, plugin packages, trusted publishers, official publishers, and guarded staff email.
ClawHub Moderation
Use the repo-local admin tool from a checked-out ClawHub repo. It wraps the existing ClawHub CLI auth/config and HTTP API surfaces. Do not call Convex internal mutations directly for staff actions.
Safety Rules
- Require an explicit target from the user: skill slug, user handle, or user id.
- Require a reason for destructive, restorative, ownership, or moderation writes.
- Before any write, show the exact command and ask for confirmation unless the
user already said to proceed or supplied
--yes. - For
email send, the user must explicitly ask for the email and sign off on the final recipient, subject, and body. Dry-run is fine for drafting. Never send until both are true, and only use--send --confirm-user-request --confirm-user-signoffafter that approval. - Prefer handles for humans. Use
--idonly when the user provides a user id. - Never bypass API-token auth, server role checks, or audit logging.
- After the write, verify state with the CLI/API and report the result.
Command Map
Run from the ClawHub repo root:
bun run admin -- --help
Authenticate or validate the current token:
bun run admin -- login
bun run admin -- whoami
Current top-level command groups:
auth
users
plugins|plugin
packages|package
org
email
skills|skill
Skills
bun run admin -- skills --help exposes:
hard-delete <skill>
unhide <slug>
revoke-version <slug>
rescan <slug>
reports
triage-report <report-id>
Examples:
