Clawhub
openclaw/openclaw
Search ClawHub for plugins by default, or skills when explicitly requested; install, verify, update, uninstall, publish, or sync skills.
A skill your agent uses for ClawHub staff moderation actions with the repo-local ClawHub admin tool: skills, users, org publishers, plugin packages, trusted publishers, official publishers, and…
$ npx skills add openclaw/clawhub --skill clawhub-moderation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openclaw/clawhub clawhub-moderation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openclaw/clawhub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/clawhub-moderation .claude/skills/clawhub-moderation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "clawhub-moderation" agent skill from https://github.com/openclaw/clawhub/tree/main/.agents/skills/clawhub-moderation into .claude/skills/clawhub-moderation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawhub-moderation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openclaw/clawhub/tree/main/.agents/skills/clawhub-moderationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openclaw/clawhub --skill clawhub-moderation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openclaw/clawhub clawhub-moderation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/clawhub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/clawhub-moderation .agents/skills/clawhub-moderation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "clawhub-moderation" agent skill from https://github.com/openclaw/clawhub/tree/main/.agents/skills/clawhub-moderation into .agents/skills/clawhub-moderation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawhub-moderation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openclaw/clawhub --skill clawhub-moderation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openclaw/clawhub clawhub-moderation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/clawhub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/clawhub-moderation .cursor/skills/clawhub-moderation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "clawhub-moderation" agent skill from https://github.com/openclaw/clawhub/tree/main/.agents/skills/clawhub-moderation into .cursor/skills/clawhub-moderation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawhub-moderation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openclaw/clawhub.git --path .agents/skills/clawhub-moderation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openclaw/clawhub --skill clawhub-moderation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openclaw/clawhub clawhub-moderation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/clawhub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/clawhub-moderation .gemini/skills/clawhub-moderation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "clawhub-moderation" agent skill from https://github.com/openclaw/clawhub/tree/main/.agents/skills/clawhub-moderation into .gemini/skills/clawhub-moderation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawhub-moderation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openclaw/clawhub clawhub-moderationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openclaw/clawhub --skill clawhub-moderation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openclaw/clawhub.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/clawhub-moderation .github/skills/clawhub-moderation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "clawhub-moderation" agent skill from https://github.com/openclaw/clawhub/tree/main/.agents/skills/clawhub-moderation into .github/skills/clawhub-moderation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawhub-moderation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openclaw/clawhub --skill clawhub-moderation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openclaw/clawhub clawhub-moderation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/clawhub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/clawhub-moderation .opencode/skills/clawhub-moderation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "clawhub-moderation" agent skill from https://github.com/openclaw/clawhub/tree/main/.agents/skills/clawhub-moderation into .opencode/skills/clawhub-moderation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawhub-moderation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
clawhub-moderationA skill your agent uses for ClawHub staff moderation actions with the repo-local ClawHub admin tool: skills, users, org publishers, plugin packages, trusted publishers, official publishers, and…
Clawhub Moderation is an agent skill from openclaw/clawhub. 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.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Skill + Plugin Registry for OpenClaw. The licence is MIT.
Read from SKILL.md and the folder at commit d044664. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
bunFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Clawhub Moderation loads about 2.1k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 660 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from openclaw/clawhub at commit d044664, republished under its MIT licence (© openclaw). 660 words, ~2,126 tokens.
.claude/skills/clawhub-moderation/SKILL.md (or your agent's skills folder).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.
--yes.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-signoff after that approval.--id only when the user provides a user id.Run from the ClawHub repo root:
bun run admin -- --helpAuthenticate or validate the current token:
bun run admin -- login
bun run admin -- whoamiCurrent top-level command groups:
auth
users
plugins|plugin
packages|package
org
email
skills|skillbun run admin -- skills --help exposes:
hard-delete <skill>
unhide <slug>
revoke-version <slug>
rescan <slug>
reports
triage-report <report-id>Examples:
bun run admin -- skills hard-delete @owner/<slug> --reason "<reason>" # dry-run
bun run admin -- skills hard-delete @owner/<slug> --reason "<reason>" --apply --confirm "<token>" --yes
bun run admin -- skills unhide <slug> --reason "<reason>" --yes
bun run admin -- skills revoke-version <slug> --version <version> --reason "<reason>" --yes
bun run admin -- skills rescan <slug> --reason "<reason>" --yes
bun run admin -- skills reports --status open
bun run admin -- skills triage-report <report-id> --status confirmed --action hide --note "<note>" --yeshard-delete requires an owner-qualified ref and defaults to a dry-run. Apply
only with the exact confirmation token returned by that dry-run.
Pass --owner <handle> to revoke-version when more than one publisher uses
the same slug.
bun run admin -- users --help exposes:
ban <handleOrId>
unban <handleOrId>
lift-moderation-hold <handleOrId>
set-role <handleOrId> <role>
reclassify-ban <handleOrId>
remediate-autobansExamples:
bun run admin -- users ban <handleOrId> --reason "<reason>" --yes
bun run admin -- users unban <handleOrId> --reason "<reason>" --yes
bun run admin -- users lift-moderation-hold <handleOrId> --reason "<reason>" --yes
bun run admin -- users set-role <handleOrId> <user|moderator|admin> --yes
bun run admin -- users reclassify-ban <handleOrId> --reason "<reason>" --apply --yes
bun run admin -- users remediate-autobans --apply --reason "<reason>"Use --id when <handleOrId> is a user id. Use --fuzzy only when the user
has asked for fuzzy handle resolution or the exact handle is ambiguous.
bun run admin -- org --help exposes:
official
create <handle>
profile update <handle>
remove-member <handle> <member>
delete <handle>
repair-scoped-packages <csv>Examples:
bun run admin -- org official list
bun run admin -- org official add <handle> --reason "<reason>" --yes
bun run admin -- org official remove <handle> --reason "<reason>" --yes
bun run admin -- org create <handle> --display-name "<name>" --member <user-handle> --role owner
bun run admin -- org profile update <handle> --bio "<description>" --reason "<reason>" --yes
bun run admin -- org profile update <handle> --logo-file <path> --reason "<reason>" --yes
bun run admin -- org remove-member <handle> <member-handle>
bun run admin -- org delete <handle> --reason "<reason>" # dry-run
bun run admin -- org delete <handle> --reason "<reason>" --apply
bun run admin -- org repair-scoped-packages <csv> # dry-run
bun run admin -- org repair-scoped-packages <csv> --applyorg create requires --member; it must not add the moderator running the
command as an implicit owner. org delete only works for empty org publishers
and defaults to dry-run. org profile update accepts a bio, a PNG/JPEG/WebP
logo under 2 MB, or both, and records the required reason in the audit log.
bun run admin -- packages --help exposes:
moderate <name>
status|moderation-status <name>
queue|moderation-queue
reports
triage-report <report-id>
hard-delete <name>
transfer <name>
repair-name <name>
migrations
set-migration <bundled-plugin-id>
trusted-publisherExamples:
bun run admin -- packages status <name>
bun run admin -- packages hard-delete <name> --owner <handle> --reason "<reason>" # dry-run
bun run admin -- packages hard-delete <name> --owner <handle> --reason "<reason>" --apply --confirm "<token>" --yes
bun run admin -- packages transfer <name> --to <owner> --reason "<reason>" # dry-run
bun run admin -- packages transfer <name> --to <owner> --reason "<reason>" --apply
bun run admin -- packages repair-name <name> --next-name <name> --reason "<reason>"
bun run admin -- packages trusted-publisher get <name>
bun run admin -- packages trusted-publisher set <name> --repository <owner/repo> --workflow-filename <file>bun run admin -- email send --help exposes:
--to <email>
--user <handle>
--subject <subject>
--body-file <path>
--body <text>
--send
--confirm-user-request
--confirm-user-signoff
--jsonDraft only:
bun run admin -- email send --user <handle> --subject "<subject>" --body-file <path>Send only after explicit request and sign-off:
bun run admin -- email send --user <handle> --subject "<subject>" --body-file <path> --send --confirm-user-request --confirm-user-signoffThe server sends through the production noreply provider and writes an audit log only after admin auth succeeds.
skills unhide.skills hard-delete, verify owner-scoped page/API reads return not found.skills unhide is a moderator manual restore. It clears skill hidden state,
applies a clean manual override to top-level moderation fields, preserves
version-level scanner records, updates public stats, and writes audit logs.skills revoke-version permanently removes one exact version, records staff
evidence, advances latest pointers to a safe survivor when one exists, and
keeps the skill independently hidden when no usable version remains.skills hide command in clawhub-admin; use report
triage with --action hide when resolving a report that should hide a skill.users ban is disruptive: it revokes API tokens, marks the user deleted,
hides owned skills, soft-deletes comments, and writes audit logs.users unban is admin-only. It clears ban state and restores skills that were
hidden by the matching ban flow; revoked API tokens stay revoked.users lift-moderation-hold is admin-only. It clears the account-level
moderation hold, restores skills hidden by that hold, and writes an audit log.packages transfer preserves the package row, stats, releases, and history;
it changes the owner publisher.packages hard-delete is admin-only, requires an already-soft-deleted package,
exact owner handle, reason, and dry-run token, and permanently removes all
package releases and related history.org delete soft-deletes an empty org publisher and retains member rows for
history; it refuses orgs with active skills or packages.© openclaw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/clawhub-moderation of openclaw/clawhub.
Open the folder on GitHubat commit d044664
Clawhub Moderation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Clawhub Moderation this skillopenclaw/clawhub | 9.5k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Clawhubopenclaw/openclaw | 392k | — | ~724 | Automated safety check: Pass | MIT | |
| Adminyc-software/qm | 15k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Clawhubtrpc-group/trpc-agent-go | 1.9k | 7 repos | ~404 | Automated safety check: Pass | Apache-2.0 | |
| ClawhubPhyAgentOS/PhyAgentOS-core | 2.8k | 3 repos | ~351 | Automated safety check: Pass | MIT | |
| Sub2API AdminWei-Shaw/sub2api | 44k | 1 repos | ~717 | Automated safety check: Pass | LGPL-3.0 |
openclaw/openclaw
Search ClawHub for plugins by default, or skills when explicitly requested; install, verify, update, uninstall, publish, or sync skills.
yc-software/qm
Act for an org admin — the admin API (scope directory, per-scope config & SOUL, any scope's memory, transcripts & captured prompts, files, user roster & external users, audit/errors/metrics/egress)…
trpc-group/trpc-agent-go
Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.com.
PhyAgentOS/PhyAgentOS-core
Search and install agent skills from ClawHub, the public skill registry.
Wei-Shaw/sub2api
Manages a Sub2API deployment from the command line: accounts, redeem and invitation codes, groups, proxies, imports, exports and raw admin API calls.
HKUDS/OpenOPC
Search and install agent skills from ClawHub, the public skill registry.
openclaw/clawhub
Creates and manages Axiom monitors and notifiers end to end through the v2 API, with scripts for each CRUD operation and a recommended create-validate-tune workflow.
openclaw/clawhub
Designs and deploys Axiom dashboards through the API, choosing chart types and writing APL or metrics queries, with templates and migration notes for Splunk and Grafana.
openclaw/clawhub
Finds unused data in Axiom by analyzing query patterns, then deploys a cost dashboard and ingest monitors to keep spend under the contract limit.
openclaw/clawhub
Explores and queries OpenTelemetry metrics in Axiom MetricsDB, listing datasets, metrics and tags first and picking the right aggregation for each metric's type.
openclaw/clawhub
Investigates incidents and production problems with hypothesis-driven debugging, queries Axiom observability data when available, and keeps secrets out of commands and output.
openclaw/clawhub
Scaffolds evaluation suites for the Axiom AI SDK: eval files, scorers, flag schemas and axiom.config.ts, generated from plain descriptions of an AI capability.
A skill your agent uses for ClawHub staff moderation actions with the repo-local ClawHub admin tool: skills, users, org publishers, plugin packages, trusted publishers, official publishers, and…. Clawhub Moderation is an agent skill from openclaw/clawhub. 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 fits situations like: clawHub staff moderation actions with the repo-local ClawHub admin tool: skills; plugin packages; trusted publishers; official publishers.
Run `npx skills add openclaw/clawhub --skill clawhub-moderation -a claude-code`. Or copy the skill folder (.agents/skills/clawhub-moderation in openclaw/clawhub) into .claude/skills/clawhub-moderation in your project. Claude Code loads it when a task matches its description.
Run `npx skills add openclaw/clawhub --skill clawhub-moderation -a codex`. Or copy the skill folder (.agents/skills/clawhub-moderation in openclaw/clawhub) into .agents/skills/clawhub-moderation in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openclaw/clawhub --skill clawhub-moderation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clawhub-moderation, .gemini/skills/clawhub-moderation, .github/skills/clawhub-moderation and .opencode/skills/clawhub-moderation in your project.
Going by SKILL.md and its folder, Clawhub Moderation needs the command-line tools its instructions call (bun).
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Clawhub Moderation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Clawhub Moderation: Clawhub (openclaw/openclaw, 392k stars), Admin (yc-software/qm, 15k stars), Clawhub (trpc-group/trpc-agent-go, 1.9k stars) and Clawhub (PhyAgentOS/PhyAgentOS-core, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
openclaw (a GitHub organization) maintains it in openclaw/clawhub, which has 9,500 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on October 8, 2026.
Source: openclaw/clawhub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.