Name: listclean
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

listclean

Listclean integration. Manage Leads, Persons, Organizations, Deals, Pipelines, Activities and more. Use when the user wants to interact with Listclean data.

Quality

61%

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/listclean/SKILL.md

Quality

Content

63%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 actionable and gives a clear, well-sequenced connection workflow with executable CLI commands and explicit state checkpoints. It is somewhat verbose in places and lacks a clean progressive-disclosure structure, with a few stub sections that add little value.

Suggestions

Trim explanatory padding Claude already knows (e.g. the 'so you can focus on the integration logic' aside and 'Use action names and parameters as needed') to improve conciseness.

Remove or expand the empty 'Listclean Overview' bullet stub (List / Column / Cleaned List) which currently conveys no actionable information.

Add a brief validation/feedback loop for CONFIGURATION_ERROR and SETUP_FAILED states (e.g. 'inspect error, re-run connection ensure, then re-poll') to push workflow clarity to 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete CLI commands, but includes some unnecessary explanation Claude already knows (e.g. 'Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic') and the 'Listclean Overview'/'Use action names and parameters as needed' filler that could be trimmed.	3 / 5
Actionability	It provides concrete, executable commands for install, login, connection ensure, polling, action search/run, and proxy requests with a flag table, covering the common cases with only minor gaps (e.g. placeholder CONNECTION_ID rather than a fully runnable end-to-end example).	4 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state handling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a polling loop, giving clear checkpoints; it falls short of 5 because recovery actions after CONFIGURATION_ERROR are left to 'check the error field' without a feedback loop.	4 / 5
Progressive Disclosure	No bundle files exist, so structure relies on section headers; the single-file body mixes overview, auth, connection, actions, proxy, and best practices inline with references only to an external docs URL, and the 'Listclean Overview' bullet stub adds little navigational value.	3 / 5
	Total	14 / 20 Passed

Description

58%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 specific to the Listclean domain and lists concrete managed entities, but its trigger guidance is generic ('interact with Listclean data') rather than tied to natural user phrases like cleaning or validating email lists. Strengthening the 'Use when' clause would lift completeness and trigger quality.

Suggestions

Add concrete trigger verbs users actually say, e.g. 'Use when the user wants to clean, validate, or verify email lists and addresses'.

Tighten the 'Use when' clause to reference Listclean-specific tasks (bounce reduction, deliverability) rather than the generic 'interact with Listclean data'.

Replace 'and more' with a couple of additional concrete entities or drop it to keep the action list comprehensive rather than open-ended.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Listclean integration') and enumerates several concrete managed objects ('Leads, Persons, Organizations, Deals, Pipelines, Activities'), giving multiple specific actions rather than vague language, though the listed items are data entities rather than operations.	4 / 5
Completeness	The 'what' is reasonably clear (manage Listclean data entities) but the 'when' is only weakly implied by 'Use when the user wants to interact with Listclean data', which is generic rather than tied to concrete trigger phrases; per the guidelines a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	It includes the app name and 'interact with Listclean data' as a natural phrase, but lacks common synonyms or the user-facing verbs ('clean', 'validate', 'email lists') a user would actually say, so keyword coverage is partial.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app (Listclean) and its entities gives it a clear niche with minimal overlap against other skills, with only minor broadness from the generic 'Manage... and more' tail.	4 / 5
	Total	14 / 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/listclean/SKILL.md
Commit: f484c82

Reviewed: 6 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.