ClawHub Reputation Gate
Checks ClawHub reputation before OpenClaw skill installation and requires explicit approval for low-scoring skills.
The files disclose the node/clawhub/openclaw dependencies, ClawHub network lookups, heuristic trust model, and confirmation flags. They also provide confirmation gating, optional manual hook wiring, signed-manifest/hash verification, and a non-mutating setup helper. Points are deducted because installation is delegated to an external suite without fully specified data flows, permission boundaries, or rollback; --confirm-reputation can bypass the reputation gate entirely, and the verification script downloads remote artifacts and removes a temporary directory.
The source includes input validation, exit codes, exception feedback, and committed tests, making the main reputation path reasonably coherent. Static review cannot establish executability; additionally, --dry-run is parsed but unused, the hook integration hard-codes threshold 70, and documentation contains minor dependency and command inconsistencies. The score therefore remains below the static ceiling.
The intended scenario, parameters, exit codes, threshold, and trigger phrases are reasonably explicit for pre-install checks on OpenClaw. Points are deducted because the skill requires clawsec-suite, clawhub, node, and openclaw, is not fit for non-OpenClaw users, depends on network access to ClawHub without mainland-China reachability guidance, and provides no Chinese usage documentation.
SKILL.md, README, skill.json, and CHANGELOG provide useful layering, installation steps, configuration, examples, limitations, licensing, version history, SBOM data, and manual integration notes. Points are deducted because maintenance ownership, update procedures, and compatibility policy are unclear; publisher identity is not verified by the FollowSkills enterprise registry; and some installation/runtime declarations are inconsistent.
The implementation combines ClawHub metadata, author activity, download counts, age, update recency, and scanner results, and requests explicit confirmation for low scores. Committed tests cover several validation cases and a malicious VirusTotal case. Static review cannot verify real outputs or network compatibility; heuristics may produce false positives or negatives, and --confirm-reputation bypasses the check, so the score is capped at the static maximum.
The source provides implementation code, a skill.json SBOM, changelog entries, signed-release verification instructions, and committed tests, enabling limited auditing. Points are deducted because tests were not executed in this review, the tests mock ClawHub rather than corroborating behavior against the real service, and there is no independent third-party review or execution evidence; under the static rules the score cannot exceed 5.
- Do not treat the heuristic reputation score as proof of safety; manually review the target skill before using --confirm-reputation.
- Reputation checks depend on ClawHub inspect/search network endpoints and may block when scanner data is unavailable; mainland-China reachability is not established.
- --dry-run is parsed but no actual dry-run behavior is shown; advisory-hook integration is manual and should be backed up and reviewed for compatibility.
- Dependencies and suite-version compatibility were not executed or independently verified in this static review.
What does this skill do, and when should you use it?
ClawHub Reputation Gate is a standalone ClawSec skill that works with the clawsec-suite guarded installer. It reads ClawHub metadata and scanner results, then applies heuristic signals such as age, update activity, author history, and downloads. Skills below the configured threshold require an explicit --confirm-reputation flag. The package also documents signed release-manifest verification, but it requires local Node.js, clawhub, OpenClaw, and clawsec-suite dependencies.
Reads skill metadata with clawhub inspect --json; evaluates scanner status and includes a VirusTotal summary when available; applies reputation heuristics based on age, updates, author history, and downloads; requires --confirm-reputation below the configured score threshold; runs the enhanced guarded installer; optionally validates local paths and prints a recommended command; downloads and verifies checksums.json, checksums.sig, the signing public key, the archive, SKILL.md, and skill.json to validate the signed manifest, public-key fingerprint, and SHA-256 hashes.
- An OpenClaw administrator wants a reputation gate before installing third-party skills through the guarded installer.
- A team installing skills from ClawHub wants scanner status and reputation signals included in its approval process.
- An operator evaluating a new or low-reputation skill wants an explicit confirmation step before proceeding.
- A maintainer installing a standalone release archive wants to verify its signed manifest before trusting or extracting package files.
What are this skill's strengths and limitations?
- Adds a separate reputation gate to the guarded installer.
- Combines scanner status, an available VirusTotal summary, age, update activity, author history, and downloads.
- Provides signed-manifest, public-key fingerprint, and SHA-256 verification steps.
- Does not rewrite files belonging to other installed skills, according to the operational notes.
- Requires clawsec-suite plus node, clawhub, and openclaw.
- Reputation scores are heuristic, and scanner results may have false positives or false negatives.
- Reputation checks call ClawHub inspect/search endpoints over the network.
- Advisory hooks are not patched automatically; the source does not provide test-coverage or cost information.
How do you install this skill?
Install the dependency first: npx clawhub@latest install clawsec-suite. Then install this skill: npx clawhub@latest install clawsec-clawhub-checker. For the Vercel Skills CLI, use: npx skills add prompt-security/clawsec --skill clawsec-clawhub-checker -a openclaw -y. For standalone releases, run the supplied verification procedure successfully before trusting or extracting the archive.
How do you use this skill?
Run: node ~/.openclaw/skills/clawsec-clawhub-checker/scripts/enhanced_guarded_install.mjs --skill some-skill --version 1.0.0. If the score is below threshold, rerun with --confirm-reputation only after review. An optional preflight is: node ~/.openclaw/skills/clawsec-clawhub-checker/scripts/setup_reputation_hook.mjs. The default threshold is 70 and can be changed with CLAWHUB_REPUTATION_THRESHOLD. Advisory-hook wiring is manual in this release.