clawsec-clawhub-checker

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

77%Weight 40%Scale 1-3

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

The content is highly actionable with strong validation checkpoints in its verification workflow, but it is somewhat verbose and keeps a large verification procedure inline rather than progressively disclosing it to a reference file.

Suggestions

Consolidate the duplicate 'Vercel Skills Installation' and 'Installation' sections into a single install path to remove redundancy.

Move the long release-artifact verification bash block into a script under scripts/ (or a references file) and keep a short summary plus a one-line invocation in SKILL.md to improve progressive disclosure.

Trim or relocate the inline homepage/license metadata that duplicates the frontmatter to tighten the body further.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands with little concept-explanation fluff, but it carries two redundant installation sections (Vercel Skills + Installation) and a large inline verification block, so it could be tightened and does not earn the score-3 'every token earns its place' anchor.	2 / 3
Actionability	It provides fully executable, copy-paste-ready commands (npx install, node script invocations with absolute paths, and a complete bash verification block), matching the score-3 anchor for concrete executable guidance.	3 / 3
Workflow Clarity	The release-artifact verification section is a clear sequenced workflow with explicit validation checkpoints (public-key fingerprint match, openssl signature verify, checksum match) and a 'only proceed after verification succeeds' gate, satisfying the score-3 anchor including feedback loops for a risky operation.	3 / 3
Progressive Disclosure	Sections are well-organized and referenced scripts (e.g. scripts/enhanced_guarded_install.mjs, scripts/check_clawhub_reputation.mjs) are real files in the bundle, but the heavy release-verification procedure is inline rather than offloaded to a reference or script, so organization could be improved beyond the score-2 anchor.	2 / 3
	Total	10 / 12 Passed

Description

57%Weight 40%Scale 1-3

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 specific and clearly niche-scoped, but it omits an explicit 'Use when...' trigger and relies on product jargon, limiting trigger-term quality and completeness.

Suggestions

Add an explicit 'Use when ...' clause naming the situations a user would actually say, e.g. 'Use when installing guarded skills from ClawHub and you want a reputation check before install.'

Replace product-specific jargon ('guarded skill installation') with broader natural terms users might say, like 'skill reputation check' or 'verify a skill before installing'.

Expand the capability list to two or three concrete actions (e.g. 'Inspects ClawHub metadata, evaluates scanner and reputation signals, and requires confirmation below threshold') to reach full specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and a concrete action ('reputation checker', 'adds a standalone reputation gate before guarded skill installation'), but does not list multiple distinct capabilities, so it falls short of the score-3 anchor.	2 / 3
Completeness	It states what the skill does, but lacks an explicit 'Use when...' trigger clause; the 'when' is only implied via 'before guarded skill installation', which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Terms like 'reputation checker', 'reputation gate', and 'skill installation' are relevant but lean on product jargon (clawsec-suite, guarded installation) rather than natural user phrasing, missing the broad coverage of the score-3 anchor.	2 / 3
Distinctiveness Conflict Risk	The description targets a clear niche (ClawHub reputation gating for clawsec-suite) with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: c6194eb

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

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.