Name: uplead
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

uplead

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

Quality

64%

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/uplead/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 content is a well-structured, mostly executable guide to driving UpLead through the Membrane CLI, with a clear connection workflow and state-based validation. Its main weaknesses are a light marketing preamble, a redundant 'Popular actions' section that repeats discovery rather than showing real UpLead actions, and shallow error-recovery detail.

Suggestions

Cut the opening product-marketing paragraph or compress it to one line; Claude can infer what UpLead is from the docs link.

In 'Popular actions', list 2-3 concrete UpLead actions with real parameters (e.g., a lead-search intent and a contact-verification endpoint) instead of restating the discovery command.

Add explicit error-recovery guidance for CONFIGURATION_ERROR/SETUP_FAILED — what to inspect in the error field and how to retry.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight CLI commands, but the opening marketing blurb ('B2B sales intelligence platform... convert prospects into customers') and a duplicated action-list command in 'Popular actions' could be trimmed without losing guidance.	3 / 5
Actionability	Commands are concrete and copy-paste ready (login, connection ensure, action list/run, request with a flags table), but 'Popular actions' reprints the discovery command instead of showing a real UpLead action or endpoint with actual parameters.	4 / 5
Workflow Clarity	The install→login→connect→poll→search→run sequence is clearly laid out with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, though CONFIGURATION_ERROR recovery guidance is only sketched.	4 / 5
Progressive Disclosure	No bundle files exist and the single-file body is well organized with clear headers; the inlined proxy flags table and 'Popular actions' duplication are minor organization gaps rather than navigation problems.	4 / 5
	Total	15 / 20 Passed

Description

61%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 cleanly answers both what and when with a distinct proper-noun trigger, but its capability list is generic ('manage data, records, automate workflows') rather than naming concrete UpLead operations. Tightening the action list to specifics like lead search and contact verification would lift specificity and trigger coverage.

Suggestions

Replace generic verbs with concrete UpLead actions, e.g. 'Search verified B2B contacts, look up company profiles, and enrich lead records.'

Expand the 'Use when...' clause with natural trigger phrases users actually say, such as 'finding leads', 'verifying contact data', or 'B2B prospecting'.

Add common synonyms or the .com/docs framing so users describing the task in different words still hit the trigger.

Dimension	Reasoning	Score
Specificity	It names the UpLead domain but the stated actions ('Manage data, records, and automate workflows') are generic and abstract rather than concrete operations like 'search leads' or 'fetch verified contacts'.	2 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with UpLead data) are present and explicit, though the trigger clause could name more specific use cases.	4 / 5
Trigger Term Quality	The natural term 'UpLead' and 'UpLead data' appear, but coverage is thin — no synonyms or related phrasings users might say such as 'leads', 'contact data', or 'B2B prospecting'.	3 / 5
Distinctiveness Conflict Risk	UpLead is a specific named product, so the trigger is highly distinct and unlikely to fire for an unrelated skill.	5 / 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/uplead/SKILL.md
Commit: f484c82

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