Name: clearhaus
Rating: 59.2 (1 reviews)
Author: membranedev

clearhaus

Clearhaus integration. Manage data, records, and automate workflows. Use when the user wants to interact with Clearhaus data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/clearhaus/SKILL.md

Quality

Content

82%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 content is a strong, executable CLI workflow with clear sequencing and good validation checkpoints in the connection phase, and it assumes Claude's competence throughout. The main gaps are a small amount of introductory padding and the absence of an explicit verify-result step for payment actions.

Suggestions

Trim the opening 'Clearhaus is a payment gateway...' paragraph and the 'so you can focus on the integration logic' aside to reduce token overhead.

Add a brief verification/check step after running financial actions (e.g. inspect the 'output' field for success status and surface errors before reporting completion).

Consider moving the proxy flag table into a short reference section or keeping it but pruning the connection-state sub-bullets that duplicate the polling instructions.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight, command-focused prose with short flag tables, but minor over-explanation remains (e.g. the opening 'Clearhaus is a payment gateway...' paragraph and 'so you can focus on the integration logic rather than auth plumbing').	4 / 5
Actionability	Every section gives copy-paste-ready, fully executable commands (install, login, connection ensure, action list/run with --input, request with a flag table) covering the common cases for a CLI-driven skill.	5 / 5
Workflow Clarity	There is a clear sequence (install → authenticate → connect → discover → run) with explicit state polling and CLIENT_ACTION_REQUIRED feedback in the connection phase; the only gap is no explicit result-verification step after running financially significant actions like charges/refunds.	4 / 5
Progressive Disclosure	With no bundle files present, all content lives inline in well-organized, clearly headed sections; structure is good, though the proxy flag table and state-handling detail are somewhat dense for a single overview file.	4 / 5
	Total	17 / 20 Passed

Description

55%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 correctly includes a 'Use when...' trigger and a brand-specific niche, but its action language ('manage data, records, automate workflows') is generic and it omits the natural payment terms users would actually say. Tightening the action list to concrete gateway operations and adding payment trigger phrases would raise specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Clearhaus operations, e.g. 'Process charges, issue refunds, and handle webhook events via the Clearhaus payment gateway.'

Add natural user trigger terms such as 'payment', 'credit card', 'charge', 'refund', or 'transaction' to the 'Use when...' clause.

Make the 'when' clause more specific, e.g. 'Use when the user wants to process payments, issue refunds, or manage Clearhaus transactions.'

Dimension	Reasoning	Score
Specificity	Names the Clearhaus domain and a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic verbs rather than concrete gateway operations like charge/refund/webhook that the body reveals.	3 / 5
Completeness	Both a 'what' ('Clearhaus integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Clearhaus data.') are present, though the 'what' is vague and the 'when' could name concrete trigger phrases.	4 / 5
Trigger Term Quality	Only 'Clearhaus' and the generic 'data' appear; the trigger phrase 'interact with Clearhaus data' is not something users naturally say, and natural payment terms (payment, charge, refund, transaction) are missing.	2 / 5
Distinctiveness Conflict Risk	The Clearhaus brand name anchors a distinct payment-gateway niche with minimal conflict risk, though the generic 'manage data' phrasing leaves minor overlap with other data-oriented skills.	4 / 5
	Total	13 / 20 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: membranedev/application-skills
Path: skills/clearhaus/SKILL.md
Commit: f484c82

Reviewed: ~9 hours 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.