Name: leadconnector
Rating: 58.4 (1 reviews)
Author: membranedev

leadconnector

LeadConnector integration. Manage Contacts, Companies, Opportunities, Users, Locations, Conversations and more. Use when the user wants to interact with LeadConnector data.

Quality

67%

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/leadconnector/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, actionable guide to the Membrane CLI flow with concrete commands, a clear connection state machine, and validation checkpoints. Its main weakness is mild verbosity (redundant sections and padded asides) and slightly loose ordering of the later action/proxy sections.

Suggestions

Remove the redundant 'Popular actions' section and the auth-plumbing aside to tighten token usage.

Reorder so 'Running actions' and 'Searching for actions' flow together, and demote the Agent-Types tangent to a brief note.

Add one explicit validation checkpoint for batch/destructive proxy requests (e.g., confirm the connection is READY and inspect the response error field before retrying) to push workflow clarity toward 5.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with code blocks and a flag table, but it includes padded asides ("so you can focus on the integration logic rather than auth plumbing"), a redundant 'Popular actions' section that restates the earlier search guidance, and an Agent-Types tangent; fits the mostly-efficient-but-could-be-tightened anchor rather than the lean anchor 4-5.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, polling, action list/run, proxy) plus an input-schema note and a flags table; the only gap is the abstract CONNECTION_ID placeholder, fitting mostly-executable-with-minor-gaps rather than the fully-copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop after user action, but later sections (Popular actions, Running actions, Proxy) are loosely ordered with minor gaps, matching clear-sequence-with-most-checkpoints rather than anchor 5.	4 / 5
Progressive Disclosure	The body is well organized with clear section headers, a single official-docs reference, and no nested/deep references; with no bundle files present, content is appropriately sized and navigable, fitting good-structure-mostly-appropriately-placed rather than the ideal clear-overview-with-one-level-references anchor 5.	4 / 5
	Total	15 / 20 Passed

Description

67%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 clearly identifies the product and lists many concrete entities with an explicit 'Use when' clause, but relies on a single trigger keyword and a generic verb ('Manage ... and more'), which limits trigger-term richness and full concreteness. It is solid but could sharpen the trigger phrases and enumerate actions more precisely.

Suggestions

Add concrete action verbs per entity (e.g., 'Create and update Contacts, search Companies, track Opportunities') instead of the generic 'Manage ... and more'.

Expand trigger terms with natural user phrases and synonyms (e.g., 'GoHighLevel', 'GHL contacts', 'LeadConnector CRM') so users phrasing it differently still match.

Tighten the 'Use when' clause with concrete triggers (e.g., 'Use when the user wants to create, search, or update LeadConnector/GoHighLevel records').

Dimension	Reasoning	Score
Specificity	Names many concrete entities ("Contacts, Companies, Opportunities, Users, Locations, Conversations") plus the action "Manage", but the verb is generic and "and more" leaves coverage gaps, fitting the several-specific-actions-with-minor-gaps anchor rather than the comprehensive anchor 5.	4 / 5
Completeness	It states what ("Manage Contacts, Companies, Opportunities, Users, Locations, Conversations and more") and when ("Use when the user wants to interact with LeadConnector data"), but the when-clause is generic rather than concrete trigger phrases, fitting the both-present-but-could-be-more-specific anchor rather than anchor 5.	4 / 5
Trigger Term Quality	The only natural trigger term is the product name "LeadConnector" ("interact with LeadConnector data"), with no synonyms or common variations; this matches the some-relevant-keywords-but-missing-variations anchor rather than the good-coverage anchor 4.	3 / 5
Distinctiveness Conflict Risk	The named product "LeadConnector" gives it a clear niche with minimal conflict risk, though the generic CRM-style "Manage Contacts, Companies..." framing carries minor overlap with related skills, matching the mostly-distinct anchor rather than the clear-niche anchor 5.	4 / 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/leadconnector/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.