Name: clearout
Rating: 55.2 (1 reviews)
Author: membranedev

clearout

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

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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 body is a well-structured, actionable integration guide with concrete CLI commands and a clear connection-state workflow including polling checkpoints. Its main weaknesses are a marketing-flavored intro and minor gaps in post-action validation and worked end-to-end examples.

Suggestions

Trim the marketing intro paragraph ('helps businesses and marketers... better deliverability and more effective marketing campaigns') and the 'so you can focus on the integration logic rather than auth plumbing' commentary.

Add an explicit validation/error-handling step after `membrane action run` — e.g., check the `output`/`error` fields and retry or surface the error before proceeding.

Include one fully-worked end-to-end example (connect → find the verify-email action → run it with a real `--input` payload → read the result) so the common case is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but includes unnecessary explanation Claude does not need, such as the marketing intro ('helps businesses and marketers clean their email lists... better deliverability and more effective marketing campaigns') and 'so you can focus on the integration logic rather than auth plumbing'. It fits anchor 3 (mostly efficient with some unnecessary explanation) rather than 4 which expects only minor trimmable instances.	3 / 5
Actionability	The skill provides concrete, executable commands throughout (membrane login, connection ensure, action list/run, request) with real flags and a popular-actions table with concrete keys. It is mostly executable with minor gaps (placeholders like CONNECTION_ID and intent QUERY require the user to fill them in), fitting anchor 4 rather than 5 which expects fully worked common-case examples.	4 / 5
Workflow Clarity	The connection setup is a clear sequenced workflow with explicit checkpoints — poll until READY, branch on BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, and re-poll after user action. It fits anchor 4 (clear sequence with most checkpoints present) rather than 5 because there is no explicit validation or error-handling step after running an action.	4 / 5
Progressive Disclosure	Content is organized into well-labeled sections (Overview, Working with Clearout, Authentication, Connecting, Searching, Popular actions, Running actions, Proxy, Best practices) with no bundle files present and everything appropriately inline. It fits anchor 4 (good structure, content appropriately placed) rather than 5 because there are no one-level-deep references, and the popular-actions and proxy-flag tables are somewhat bulky inline.	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 has an explicit 'Use when' trigger and is tied to a named product, giving it solid completeness and distinctiveness, but the capability description is generic and lacks the concrete email-verification actions a user would naturally associate with Clearout. Trigger terms miss the natural email-related phrasing users would actually say.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Clearout actions such as 'verify email addresses, clean email lists, and enrich leads'.

Expand the trigger clause to include natural user phrases, e.g. 'Use when the user wants to verify emails, clean an email list, validate an address, or enrich leads.'

Mention the email-verification niche explicitly so the description is clearly distinguishable from generic data-integration skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Clearout integration') but the stated actions — 'Manage data, records, and automate workflows' — are generic and not concrete (no mention of email verification, list cleaning, or lead enrichment). This matches the anchor where the domain is named but actions are minimal or generic; it does not reach 3 because the actions lack the concreteness of 'extracts content'.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Clearout data') are present, with an explicit 'Use when' clause. It does not reach 5 because the 'what' is generic rather than concrete trigger phrases, and is above 3 because the 'when' is explicit rather than weakly implied.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Clearout data' includes the product name and 'data', but misses the natural phrases users would say such as 'verify emails', 'clean email list', or 'email validation'. It has some relevant keywords but is missing common variations, fitting anchor 3 rather than 4 which expects broader keyword coverage.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named product 'Clearout' and the trigger 'interact with Clearout data' makes it mostly distinct with only minor overlap risk against other data-management skills. It falls short of 5 because the generic 'manage data, records, automate workflows' phrasing could overlap with broader integrations.	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/clearout/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.