Name: lemlist
Rating: 62.4 (1 reviews)
Author: membranedev

lemlist

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

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/lemlist/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 highly actionable with executable commands covering the full Membrane workflow and a clear state-driven connection process, held back only by minor verbosity and a small navigation gap around the unlabeled 'Step 2'.

Suggestions

Label the 'Searching for actions' section as 'Step 2' (or restructure the numbered steps) so the repeated 'skip to Step 2' references resolve.

Trim the marketing phrasing in the intro and the 'who uses Lemlist' sentence to keep the body lean.

Consider moving the proxy flag table and full clientAction state details into a references file to shorten the main SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables with only minor over-explanation, such as the marketing-style intro ('so you can focus on the integration logic rather than auth plumbing') and the brief 'who uses Lemlist' sentence that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for every common case — install, login, connection ensure/get with --wait, action list/run with --input, and the proxy request with a full flag table — with clearly marked placeholders.	5 / 5
Workflow Clarity	The install → authenticate → connect → poll-for-ready → search → run sequence is clear with a state-machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but the repeated 'skip to Step 2' references an unlabeled Step 2, a minor sequencing gap.	4 / 5
Progressive Disclosure	Sections are well-organized with a clear overview and grouped topics, and no bundle files exist so all content is appropriately inline; the only gap is that the substantial proxy-flag table and connection-state details could optionally live in a reference file for a skill of this length.	4 / 5
	Total	17 / 20 Passed

Description

66%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 answers both what the skill does and when to use it and is highly distinct thanks to the named app, but its action list is generic and its trigger terms lack synonyms a user would naturally say.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Lemlist capabilities such as campaigns, leads, steps, and email accounts.

Expand the trigger clause to include natural synonyms users say, e.g. 'Use when the user wants to manage Lemlist campaigns, leads, or outreach sequences.'

Keep the third-person voice but make the 'when' clause name the specific objects users work with rather than the generic 'Lemlist data'.

Dimension	Reasoning	Score
Specificity	Names the Lemlist domain plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Lemlist capabilities like campaigns, leads, or email accounts, so it is not comprehensive.	3 / 5
Completeness	Both 'what' (Lemlist integration, manage data/records, automate workflows) and 'when' ('Use when the user wants to interact with Lemlist data') are present and explicit, though the 'when' clause is generic and could be more specific.	4 / 5
Trigger Term Quality	It includes the natural keyword 'Lemlist' via 'interact with Lemlist data', but misses common variations or synonyms a user might say such as 'outreach', 'cold emails', 'campaigns', or 'leads'.	3 / 5
Distinctiveness Conflict Risk	Lemlist is a named third-party app, so the trigger 'Lemlist' carves out a clear niche with minimal risk of firing for an unrelated skill.	5 / 5
	Total	15 / 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/lemlist/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.