CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clearhaus

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

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/clearhaus/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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, actionable CLI workflow guide with good error-state handling for the connection lifecycle. Its weaknesses are padded introductory sections, a filler entity-overview tree, and a dangling 'Step 2' reference that breaks the workflow's navigation.

Suggestions

Fix the dangling references: either label the steps explicitly (Step 1: connect, Step 2: discover and run actions) or replace 'skip to Step 2' with the actual section name.

Cut the 'Clearhaus is a payment gateway...' intro paragraph and the entity-name overview tree — Claude can get the domain from the description and discover entities via 'action list'.

Add one worked example of running a real Clearhaus action (e.g. listing charges or creating a refund) with concrete parameters to bridge discovery and execution.

DimensionReasoningScore

Conciseness

The body is mostly command-driven, but includes unnecessary padding: the 'Clearhaus is a payment gateway...' intro paragraph, a bare entity-name overview tree ending in filler ('Use action names and parameters as needed'), and asides like 'This is the fastest way to get a connection.'.

3 / 5

Actionability

Concrete copy-paste CLI commands cover install, login (including headless code completion), connection setup, polling, action discovery/run with JSON input, and proxy requests with a flags table; the only gap is a worked example with a real Clearhaus action and parameters.

4 / 5

Workflow Clarity

The sequence (install → authenticate → connect → poll to READY → discover actions → run → proxy fallback) is clear, with an explicit connection-state checkpoint loop enumerating READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR and next steps for each. Minor gaps: 'skip to Step 2' is referenced twice but no Step 2 is labeled, and there is no Step 1 header.

4 / 5

Progressive Disclosure

Single-file skill (~140 lines) with no bundle files, well-organized sections, and a link to official docs; nothing is buried. The proxy flags table and entity overview could be trimmed but placement is appropriate.

4 / 5

Total

15

/

20

Passed

Description

57%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 and includes an explicit 'Use when' trigger tied to the Clearhaus brand, but it is thin on substance: no concrete capabilities and no domain keywords beyond the product name. It reads as a generic template with the app name substituted.

Suggestions

Replace 'Manage data, records, and automate workflows' with 2-3 concrete Clearhaus capabilities, e.g. 'Process payments, issue refunds, and manage chargebacks and webhooks via the Clearhaus payment gateway'.

Add natural trigger terms users would actually say — payments, transactions, refunds, payouts — to the 'Use when' clause, e.g. 'Use when the user mentions Clearhaus, wants to process a payment or refund, or asks about transaction records'.

State the integration mechanism in one clause (via the Membrane CLI) so the what is specific rather than templated.

DimensionReasoningScore

Specificity

The description names the domain ('Clearhaus integration') but the actions are generic — 'Manage data, records, and automate workflows' could apply to any app connector, and no concrete Clearhaus-specific actions (payments, charges, refunds) are listed.

2 / 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; the when is explicit but generic and the what is vague, so it sits just below anchor 5.

4 / 5

Trigger Term Quality

'Clearhaus' is a relevant keyword and the 'Use when... Clearhaus data' clause gives one trigger, but common natural phrases users would say — payments, refunds, charges, transactions, payment gateway — are missing.

3 / 5

Distinctiveness Conflict Risk

The Clearhaus brand name pins a distinct niche with low conflict risk, but the templated generic phrasing ('Manage data, records, and automate workflows') overlaps with any sibling integration skill following the same template.

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

membranedev/application-skills

Path

skills/clearhaus/SKILL.md

Revision

f484c82

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill