clawhub-clawscan
Skill9.6k starsChanged 13 days agoMITView on GitHub
Investigate ClawScan health alerts, diagnose scanner or ClawHub integration failures, prepare operational repairs, and route validated verdict inaccuracies upstream. Account ban appeals use clawhub-ban-appeals.
2 other projects use a version of this; 2 new projects in the last 4 weeks, against 0 the 4 before.
Adopted by
Surging: 2 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- clawdbot/clawdhubword for word, first seen Nov 1, 2026
- openclaw/clawhubword for word, first seen Nov 1, 2026
Other versions2 projects use a version of this.
Word for word · 2
- openclaw/clawhub★ 9.6k100% same
- clawdbot/clawdhub★ 9.6k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- autoreviewSkill
- axiom-alertingSkill
- axiom-sreSkill
- building-dashboardsSkill
- clawhub-ban-appealsSkill
- clawhub-content-rights-correspondenceSkill
- clawhub-convexSkill
- clawhub-featuredSkill
- clawhub-moderationSkill
- clawhub-pr-maintainerSkill
- clawhub-production-releaseSkill
- controlling-costsSkill
- convex-acquire-domainSkill
- convex-addSkill
- convex-advisorSkill
- convex-agentSkill
- convex-authSkill
- convex-authzSkill
- convex-backupSkill
- convex-billingSkill
- convex-check-updatesSkill
- convex-costSkill
- convex-create-componentSkill
- convex-cronsSkill
- convex-deploy-guardSkill
- convex-designSkill
- convex-docsSkill
- convex-domainsSkill
- convex-envSkill
- convex-expertSkill
- convex-explain-appSkill
- convex-improve-convex-pluginSkill
- convex-insightsSkill
- convex-launch-readinessSkill
- convex-migrate-rehearseSkill
- convex-migrateSkill
- convex-migration-helperSkill
- convex-monitorSkill
- convex-optimizeSkill
- convex-performance-auditSkill
- convex-quickstartSkill
- convex-retentionSkill
- convex-reviewerSkill
- convex-seedSkill
- convex-self-healSkill
- convex-sentinelSkill
- convex-setup-authSkill
- convex-shipSkill
- convexSkill
- convex-suggestSkill
- convex-testSkill
- convex-verifySkill
- create-and-cleanup-migrationSkill
- openclaw-brandSkill
- openclaw-carapaceSkill
- openclaw-design-auditSkill
- openclaw-designSkill
- openclaw-design-systemSkill
- openclaw-marketing-pagesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
If the request is an account-ban appeal, route it to clawhub-ban-appeals.
- Very specific: line 40
Read evidence and tools for the applicable read surface.
- Very specific: line 101
Read upstream reporting. Every validated accuracy complaint is deduplicated and tracked in openclaw/clawscan, including SkillSpector/AIG …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ClawScan response
Turn an alert or scan complaint into an evidence-backed disposition, an authorized repair, or a report to the component owner. Run from a ClawHub checkout. This skill grants no deployment, moderation, publication, or communication authority; use the authority supplied with the task and the applicable repository skills.
Intake and delegation
Admin owns intake and the final notification. Delegate substantial investigation through the existing runtime so its main session stays available. Read the active workspace's delegation guidance and discover its actual session tools before choosing parameters. Delegating substantial work is instruction/prompt guidance, shaped by workspace policy and runtime defaults; it is not enforced by the spawn engine. Session creation, tool access, and delivery are runtime behavior.
Pass the alert permalink, firing time/window, environment, query/run links, known job or artifact identity, this skill's path, allowed actions, and required return destination to the worker. Include already-active investigation context to avoid duplicate repairs. Use native child status and completion handling; follow the accepted spawn receipt for result delivery. Do not invent a delegation API, impose a worker cap, add a progress database, or schedule another health job.
Workers return evidence and decisions to the requesting Admin session. Admin reviews the result and posts the notification in its established thread. A worker completion establishes neither deployment nor production acceptance.
If the request is an account-ban appeal, route it to clawhub-ban-appeals. That skill may supply a scanner inaccuracy for the upstream-reporting branch below; it retains ownership of the appeal decision.
Establish what happened
Read evidence and tools for the applicable read surface. Correlate the alert window with the exact run/job/attempt and a fresh observation of the same environment. Record observation times, observed impact, completed versus failed attempts, and current queue/run state when relevant. Report unavailable coverage explicitly; missing data is not health.
Choose the supported disposition before changing anything:
Record alert validity at firing time separately from actionability now. A real failure that later recovered remains a true historical failure; describe it as currently recovered/non-actionable only to the extent fresh evidence supports.
| Disposition | Evidence and next action |
| Confirmed active incident | Current evidence corroborates availability, queue, integrity, or security impact. Locate the failing boundary and repair within authority or hand off to its owner. |
| Operational failure | An attempt timed out, failed a scanner/judge stage, rejected a receipt/schema, or failed claim/upload/completion. Establish current impact and ownership; a failed attempt is not a malicious verdict. |
| Completed-verdict disagreement | The exact artifact has a completed verdict whose accuracy is disputed. Inspect the cited behavior and validate the complaint before reporting an inaccuracy. |
| False or non-actionable alert | Evidence demonstrates a duplicate, historical/recovered condition, expected behavior, or an incorrect query interpretation. Give the counter-evidence; propose alert correction only if warranted. |
| Insufficient evidence | Identify the precise missing run, artifact, current read, or access. Return what is established and the next useful read; leave the unresolved conclusion open. |
A completed malicious or suspicious verdict can be operationally healthy. An orchestrator that exited successfully can still contain a failed scanner or unusable judge result. Check the relevant stage and consumer validation, not just the workflow conclusion. Preserve concurrent valid security findings when one finding is wrong.
Attribute the defect
Trace the first failing boundary, using exact input/output evidence and deployed versions. Separate a confirmed cause from an unverified candidate.
| Owner | Boundary to verify |
ClawHub (openclaw/clawhub) | Dispatch, queue/lease handling, artifact construction, worker environment, report mapping/storage, moderation or public trust presentation. A correct raw result mapped incorrectly belongs here. |
ClawScan (openclaw/clawscan) | Native orchestration, built-in static rules, artifact/receipt contract, adapters, or judge synthesis. Attribute downstream evidence separately from the final judge decision. |
| NVIDIA SkillSpector | The skillspector report, scanner execution, or native detection. Record whether the fault occurs in upstream code or a ClawScan-maintained adapter/patch. |
| Tencent AIG / AI-Infra-Guard | The aig report or aig-skill-scan execution/detection. Distinguish upstream scanner behavior from the local adapter and judge interpretation. |
An external provider or host dependency can be the operational cause; keep its attribution explicit rather than forcing it into a scanner verdict defect. If evidence spans components, name the primary failing boundary and contributing components. Do not guess an upstream repository from a report's display label.
Repair or route
For a confirmed repairable defect, use an isolated checkout and the existing code/test seams. Demonstrate the failure and changed behavior with the same input or a faithful sanitized regression. Run the touched repository's relevant checks. For Convex changes, first read clawhub-convex; production deployment follows clawhub-production-release.
Operational actions such as dispatching workers, rescanning, changing config, deploying, or restoring content require the task's corresponding authority. A repair task does not permit new release gates, model/provider changes, broader security exceptions, or retries until a preferred verdict appears. If another owner is already repairing the incident, return relevant new evidence to that owner instead of starting a competing recovery.
Validated scanner inaccuracies
Read upstream reporting. Every validated
accuracy complaint is deduplicated and tracked in openclaw/clawscan, including
SkillSpector/AIG findings and ClawHub-only verdict mapping defects. For the latter,
tag the report as ClawHub integration and link the primary ClawHub repair; do not
misattribute it to a scanner. Pure operational failures do not require an accuracy
report. Link an existing issue or prepare a new report with
component attribution, exact versions, reproduction, and analysis. Further
reporting to NVIDIA/Tencent follows the component's contribution/security policy
and task authority; preserve the ClawScan tracking link.
Accuracy repair should generalize to the observed failure mechanism. Do not add per-package verdict exceptions, suppress valid findings, or bypass scanning to settle a complaint. Account or listing restoration remains a separate moderation decision.
Return to Admin
Return a concise result through the runtime's existing parent/session path:
- Disposition, environment, alert/source link, and observation time.
- Confirmed impact and component owner, with evidence links and any uncertainty.
- Repair or report outcome: exact changes/commits, regression before/after, checks, existing upstream link or a ready-to-publish draft.
- Actions actually executed versus prepared, current verification limits, and any exact missing input or decision needed.
Admin verifies the evidence and uses its normal notification path. Keep private authority, account identifiers, and deployment configuration in the active workspace; public skill content is reusable procedure.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

