Name: leadconduit
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

leadconduit

LeadConduit integration. Manage Recordses. Use when the user wants to interact with LeadConduit data.

Quality

66%

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

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 an actionable, well-structured guide to the Membrane CLI workflow for LeadConduit, with strong command coverage and a clear connection state machine. Small fixes — trimming marketing prose, reconciling the 'Popular actions' heading, and labeling 'Step 2' consistently — would round it out.

Suggestions

Reconcile the 'Popular actions' section: either list a few concrete popular actions or rename the heading to 'Discovering actions'.

Label the workflow steps consistently (e.g. '## Step 1: Connect', '## Step 2: Search & run actions') so the 'Skip to Step 2' references resolve.

Trim marketing prose such as 'so you can focus on the integration logic rather than auth plumbing' and 'This will burn less tokens' for tighter token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-focused with copy-paste CLI blocks, though a few marketing-ish lines ('auth plumbing', 'burn less tokens') could be trimmed without losing clarity.	4 / 5
Actionability	Concrete executable commands (login, connection ensure, action run, request) cover the common cases, but the 'Popular actions' heading promises actions while delivering only a discovery command, a minor gap.	4 / 5
Workflow Clarity	The connection flow is a clear state machine with polling checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but 'Step 2' is referenced without a consistently labeled step structure.	4 / 5
Progressive Disclosure	No bundle files exist and none are needed for this CLI-driven skill; sections are well-organized into clear headers, justifying a high score though it runs longer than the simple-skill threshold.	4 / 5
	Total	16 / 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 correctly pairs a named product with an explicit 'Use when' trigger, satisfying the completeness and distinctiveness bars, but it relies on a single vague action verb and thin keyword coverage. Tightening 'Manage Recordses' into concrete operations and adding synonyms would lift specificity and trigger quality.

Suggestions

Replace the generic 'Manage Recordses' with concrete operations, e.g. 'Create, read, update, delete, and list Records in LeadConduit'.

Add natural trigger synonyms users might say, such as 'leads', 'LeadConduit records', or 'LeadConduit data' alongside 'interact with LeadConduit data'.

Fix the malformed plural 'Recordses' to 'Records' to read more naturally.

Dimension	Reasoning	Score
Specificity	The description names the LeadConduit domain but the only action verb is the generic 'Manage Recordses' (a malformed plural of the Records entity), which is minimal rather than a list of concrete operations.	2 / 5
Completeness	Both a 'what' ('LeadConduit integration. Manage Recordses.') and an explicit 'when' ('Use when the user wants to interact with LeadConduit data.') are present, though the 'what' is brief and could be more specific.	4 / 5
Trigger Term Quality	It surfaces the natural product keyword 'LeadConduit' and the phrase 'interact with LeadConduit data', but misses common variations or synonyms a user might actually say.	3 / 5
Distinctiveness Conflict Risk	LeadConduit is a named product giving a clear niche with distinct triggers and minimal conflict risk, but the generic 'interact with LeadConduit data' phrasing leaves minor overlap with adjacent integration skills.	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/leadconduit/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.