CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clawsec-clawhub-checker

ClawHub reputation checker for clawsec-suite. Adds a standalone reputation gate before guarded skill installation.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/clawsec-clawhub-checker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The body is highly actionable with executable commands, explicit validation, and clear safety framing, which is its core strength. Its weaknesses are structural: a large inline verification script that belongs in a separate file, a dangling reference to a non-existent hooks/ path, and some redundancy between Operational Notes and the frontmatter.

Suggestions

Move the Release Artifact Verification bash block into scripts/ (e.g. verify_release.mjs or verify_release.sh) and keep a one-line invocation plus the pubkey fingerprint in SKILL.md, reclaiming ~70 lines of context.

Fix or remove the reference to hooks/clawsec-advisory-guardian/lib/reputation.mjs — the file does not exist in the bundle, so the manual wiring instructions cannot be followed as written.

Consolidate the three installation paths (Vercel Skills CLI, clawhub install, direct enhanced_guarded_install.mjs) into one section with a short decision note, and drop the Operational Notes lines that duplicate frontmatter requires/depends_on.

DimensionReasoningScore

Conciseness

Mostly efficient and operational with no tutorials on concepts Claude already knows, but the ~70-line Release Artifact Verification bash script is inlined wholesale in SKILL.md and 'Operational Notes' restates the frontmatter's requires/depends_on, so it could be tightened.

3 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: exact install commands, a complete signed-manifest verification script with set -euo pipefail, fingerprint checks, and error exits, concrete usage invocations with flags, an exit-code table, and a documented environment variable with its default.

5 / 5

Workflow Clarity

There is a clear sequence with explicit validation checkpoints (fingerprint mismatch exits 1, 'Only install or extract the archive after this verification succeeds') and a feedback loop (below-threshold score requires rerunning with --confirm-reputation), but the install flow is fragmented across three alternative paths and the advisory-hook wiring is left manual, leaving minor gaps versus the level-5 anchor.

4 / 5

Progressive Disclosure

Sections are well organized and all three scripts/ references resolve to real bundle files, but the 70-line verification block is inline content that belongs in a separate script or reference file, and the body references hooks/clawsec-advisory-guardian/lib/reputation.mjs which does not exist in the bundle.

3 / 5

Total

15

/

20

Passed

Description

53%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.

The description is concise, third-person, and clearly states what the skill does, but it is a single-action statement with no 'when to use it' trigger guidance and jargon-heavy keywords. It is a serviceable but incomplete description rather than a strong one.

Suggestions

Add an explicit trigger clause, e.g. 'Use when installing skills from ClawHub and you need a reputation/security check before guarded installation.'

Enumerate the concrete actions the checker performs (reads ClawHub metadata, evaluates scanner/VirusTotal status, applies age/update/author/download heuristics, gates on --confirm-reputation) so specificity reaches the several-actions level.

Include a couple of natural user-facing synonyms alongside the product names (e.g. 'skill reputation', 'malicious skill check', 'ClawHub score') to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('ClawHub reputation checker') and one concrete action ('Adds a standalone reputation gate before guarded skill installation'), but stops at a single action rather than the several specific actions of the level-4 anchor.

3 / 5

Completeness

The 'what' is clear (a standalone reputation gate before guarded skill installation), but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'reputation checker', 'reputation gate', and 'guarded skill installation' are relevant to the niche but are largely product-proper-noun jargon; common natural variations and synonyms a user would say are missing, so it sits between the generic level 2 and good-coverage level 4.

3 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (ClawHub reputation gating for the clawsec-suite installer) with distinct triggers, though it explicitly builds on the closely related clawsec-suite guarded installer, creating minor overlap risk with that sibling skill.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

prompt-security/clawsec

Path

skills/clawsec-clawhub-checker/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.