CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clawhub-moderation

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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An actionable, verification-conscious moderation reference whose executable command coverage is excellent. The main gaps are structural: the bulk command catalog is monolithically inlined in SKILL.md with no progressive disclosure, and the workflow lacks error-recovery guidance for failed or wrong-target writes.

Suggestions

Move the per-command example catalogs (Skills, Users, Org, Plugin Packages, Staff Email) into a one-level-deep reference file such as references/commands.md, keeping Safety Rules, the command map overview, and Verification in SKILL.md so the main file acts as an overview.

Add error-recovery guidance to the Verification section: what to do when a write fails mid-operation, when verification shows an unexpected state (e.g., wrong target), and how to roll back or escalate — completing the feedback loop for destructive operations.

Trim the duplication between the ```text command listings and the example blocks (e.g., drop redundant trivial examples like 'packages status <name>' or fold the dry-run/apply pairs into a single annotated example) to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is a lean, reference-dense command catalog with no concept teaching — every section conveys non-obvious operational detail ('hard-delete requires an owner-qualified ref and defaults to a dry-run', 'queueing a scan is a moderation write'). Minor redundancy keeps it below 'every token earns its place': command names are listed in text blocks and then repeated verbatim in the example blocks, and both dry-run and --apply variants are shown for several commands.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with clearly marked placeholders cover every command group, e.g., 'bun run admin -- skills hard-delete @owner/<slug> --reason "<reason>" --apply --confirm "<token>" --yes', plus flag caveats (--owner, --fuzzy, --id) and dry-run/apply pairs — matching the top anchor for covering the common cases.

5 / 5

Workflow Clarity

Validation is present, not missing, so the destructive-operation cap at 3 does not apply: dry-run defaults with confirmation tokens, mandatory --yes, a pre-write confirmation rule ('Before any write, show the exact command and ask for confirmation'), and a dedicated Verification section with per-category post-write checks. It falls short of the top anchor because there is no error-recovery guidance (what to do when verification shows an unexpected state or a write fails) and the sequence is distributed across Safety Rules and Verification rather than one ordered checklist.

4 / 5

Progressive Disclosure

The single ~240-line file is well-sectioned (Safety Rules, Command Map, Verification, Impact Notes) but inlines the full per-command example catalog and impact notes that belong one level deep in reference files, with no external references at all — matching the anchor 'content that should be separate is inline'. The under-50-line simple-skill exception does not apply, and structure is too good for the 'minimal structure' anchor.

3 / 5

Total

16

/

20

Passed

Description

73%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A distinctive, well-scoped description with strong trigger nouns and explicit 'Use for' guidance, held back by generic action language. Replacing the abstract phrase 'moderation actions' with the concrete operations (ban/unban users, hide or hard-delete skills, transfer packages, send guarded staff email) would raise both specificity and trigger coverage.

Suggestions

Replace the generic phrase 'staff moderation actions' with concrete operation verbs, e.g., 'ban and unban users, hide or hard-delete skills, transfer plugin packages, triage reports, and send guarded staff email', so specificity reaches the 'lists several specific actions' anchor.

Add an explicit 'Use when...' clause naming natural user requests (e.g., 'Use when a staff member asks to ban a ClawHub user, remove a skill or package, or send an official staff email') to add action-level trigger phrases and lift completeness.

DimensionReasoningScore

Specificity

The description names the domain ("ClawHub staff moderation actions"), the specific tool ("repo-local ClawHub admin tool"), and enumerates seven concrete target categories ("skills, users, org publishers, plugin packages, trusted publishers, official publishers, and guarded staff email"), which is more concrete than a bare domain claim. However, the only action language is the generic phrase "moderation actions" — no concrete verbs like ban, hide, hard-delete, or send — so it does not reach the 'lists several specific actions' anchor.

3 / 5

Completeness

It answers both questions: the what is the admin tool and its enumerated moderation scopes, and the opening "Use for ClawHub staff moderation actions" is equivalent explicit trigger guidance, so the missing-'Use when' cap at 3 does not apply. It is not a 5 because the when is merged with the what in a single clause and lacks separate concrete trigger phrases (e.g., 'Use when asked to ban a user or delete a skill').

4 / 5

Trigger Term Quality

Good natural keyword coverage: "moderation", "staff", "admin", "ClawHub", "skills", "users", "org publishers", "plugin packages", and "staff email" are terms a user would naturally say when needing this skill. It falls short of comprehensive because common action-verb triggers users would actually utter (ban, unban, hide, delete, transfer, triage) are missing.

4 / 5

Distinctiveness Conflict Risk

"ClawHub staff moderation actions with the repo-local ClawHub admin tool" carves out a clear platform-specific, staff-only niche with distinct triggers; no other skill would plausibly collide with it, matching the minimal-conflict anchor.

5 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openclaw/clawhub

Path

.agents/skills/clawhub-moderation/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.