CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clearout

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

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

75%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 a strong, execution-focused guide: concrete CLI commands for every phase, an explicit connection-state feedback loop, and a sensible fallback to proxied raw API calls. The main flaws are cosmetic — broken step cross-references ("skip to Step 2" with no Step 2 defined), a few marketing sentences, and the absence of a worked example invoking a real Clearout action with sample parameters.

DimensionReasoningScore

Conciseness

The body is dominated by lean, executable command blocks (install, login, connection ensure, polling, action search/run, proxy flags) with only minor over-explanation, e.g., the marketing filler "This ensures better deliverability and more effective marketing campaigns" and "so you can focus on the integration logic rather than auth plumbing". This fits "Efficient; minor instances of over-explanation that could be trimmed"; it is not a 5 because a few promotional/padded sentences could be cut, and not a 3 because the padding is minor rather than a pattern.

4 / 5

Actionability

Nearly everything is copy-paste ready: `npm install -g @membranehq/cli@latest`, `membrane connection ensure "https://clearout.io/" --json`, `membrane action list --connectionId=... --intent "QUERY"`, `membrane action run <actionId> --input '{...}'`, plus a full proxy-flag table. It falls short of anchor 5 only because no worked example shows an actual action from the Popular actions table (e.g., `verify-email` with a real email parameter) being invoked, leaving the most common use case as a template rather than a specific example.

4 / 5

Workflow Clarity

The sequence (install → login → connection ensure → poll until READY → search actions → run → proxy fallback) is clear, and the polling section enumerates states with explicit recovery paths (CLIENT_ACTION_REQUIRED → show uiUrl/agentInstructions → poll again; CONFIGURATION_ERROR/SETUP_FAILED → check the error field), which is a genuine feedback loop. It is not a 5 because the step numbering is broken — the text says "skip to Step 2" twice but no "Step 2" heading exists — and no verification is described after running an action or proxy request.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the ~150-line body is organized into clear, well-signaled sections (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) that keep everything one level deep and navigable. It is not a 5 because the skill exceeds the simple-skill threshold and inlines bulk reference-like content — the Popular actions table and the proxy flag table — that would sit more appropriately in a references file; there are no dangling or buried references, so it is above a 3.

4 / 5

Total

16

/

20

Passed

Description

37%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 a generic integration-template placeholder rather than a description of Clearout's actual capability (email verification and lead enrichment). It never mentions email verification, the skill's core function, and its trigger guidance is circular. Distinctiveness is saved only by the brand name.

Suggestions

Replace "Manage data, records, and automate workflows" with the concrete capabilities: e.g., "Verify email addresses (syntax, MX, SMTP, disposable, catch-all, role-account checks), find business emails by name and domain, and check your Clearout credit balance."

Rewrite the trigger clause with natural user phrasing: e.g., "Use when the user mentions Clearout, wants to verify or validate email addresses, clean an email list, or find a contact's email address."

State the "what" explicitly — email verification and lead enrichment — instead of the circular "interact with Clearout data", which never tells Claude what domain the skill operates in.

DimensionReasoningScore

Specificity

The description names the domain ("Clearout integration") but its actions are pure template boilerplate — "Manage data, records, and automate workflows" — with no concrete mention of what Clearout actually does (email verification, disposable/catch-all checks, email finding). This matches the anchor "Names the domain but actions are minimal or generic"; it does not reach 3 because no concrete, Clearout-specific action is listed.

2 / 5

Completeness

A "Use when" clause is present ("Use when the user wants to interact with Clearout data") but is circular — it restates the domain rather than giving trigger conditions — and the "what" ("Manage data, records, and automate workflows") is vague, never stating email verification or lead enrichment. It sits between anchor 2 (vague what, weak when) and anchor 4 (both present, when could be more specific): both halves exist but neither is clear, so 3 is the best fit.

3 / 5

Trigger Term Quality

The only real keyword is the brand name "Clearout"; the natural phrases a user would say — "verify an email address", "clean my email list", "find someone's email", "check if an email is disposable" — are entirely absent, matching "One or two generic keywords; missing the natural phrases users say". It is not a 3 because "data", "records", and "workflows" add no relevant search terms beyond the brand name.

2 / 5

Distinctiveness Conflict Risk

The brand name "Clearout" gives it a distinct anchor for users who name the tool, but the generic tail "Manage data, records, and automate workflows" is shared boilerplate that would overlap with any sibling integration skill using the same template, fitting "Somewhat specific but could still overlap with similar skills". It is not a 4 because a request to simply "manage data" or "automate workflows" would plausibly trigger it alongside many other skills.

3 / 5

Total

10

/

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/clearout/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.