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

leandata

LeanData integration. Manage data, records, and automate workflows. Use when the user wants to interact with LeanData 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/leandata/SKILL.md

Quality

Content

76%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 highly actionable with copy-paste-ready Membrane CLI commands and a well-organized single-file structure. Its weaknesses are workflow coherence — dangling 'Step 2' references and no validation for destructive proxy/action operations — and minor verbosity in the overview and a few padded phrases.

Suggestions

Fix the step numbering: label the connect section '1a', keep '1b' for the wait step, and add an explicit 'Step 2: Search for actions' header so the 'skip to Step 2' reference resolves.

Add a validation checkpoint after destructive proxy requests and action runs, e.g. re-fetch or inspect the `output` field and confirm the expected state before proceeding.

Trim the redundant 'LeanData Overview' bullet list and the 'rather than auth plumbing' phrasing to tighten the opening.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight command references, tables, and flagged examples with only minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' and a brief opening background paragraph. It fits 'Efficient; minor instances of over-explanation that could be trimmed' and is not a 5 because those padded phrases and the thin 'LeanData Overview' section could be cut.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering install, login, connection ensure/get with --wait, action list/run with --input JSON, and proxy requests with a complete flag table. This matches 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases.'	5 / 5
Workflow Clarity	A sequence exists (install → auth → connect → poll for READY → search → run) and the connection step has explicit state-based checkpoints, but the numbering is incoherent ('skip to Step 2' with no Step 2 header, '1b' with no '1a') and destructive proxy operations (DELETE/PUT) plus action runs lack any validation/verification step. Per the rubric, missing validation for destructive/batch operations caps this at 3; it is not a 4 because of those validation gaps.	3 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent) and the skill is a single self-contained file with clear section headers and a flag table, so structure is good. It matches 'Good structure; most content is appropriately placed; minor organization gaps' — the redundant 'LeanData Overview' section and thin bullet list are the minor gap — and is not a 5 because that thin overview duplicates the intro and could be consolidated.	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 identifies the LeanData niche and includes both a 'what' and a 'Use when' clause, but its action language is generic and its triggers rely almost entirely on the product name. It is serviceable yet light on concrete capability detail and trigger variations.

Suggestions

Replace generic verbs with LeanData-specific capabilities, e.g. 'route and match leads, manage lead-to-account matching, and automate routing workflows.'

Broaden the trigger with concrete user phrases such as 'Use when the user wants to route leads, match leads to accounts, or manage LeanData records.'

Drop the redundant 'data' after LeanData in the trigger to avoid the generic 'interact with LeanData data' phrasing.

Dimension	Reasoning	Score
Specificity	The description names the LeanData domain but its actions — 'Manage data, records, and automate workflows' — are generic and abstract rather than concrete (it never mentions LeanData's actual capabilities like lead routing or matching). It matches the anchor 'Names the domain but actions are minimal or generic' and falls below anchor 3, which requires 1-2 concrete actions.	2 / 5
Completeness	Both 'what' ('LeanData integration. Manage data, records, and automate workflows.') and 'when' ('Use when the user wants to interact with LeanData data.') are present, satisfying the anchor for having both with a 'when' that could be more specific. It is not a 5 because the trigger phrases are generic rather than concrete, and not a 3 because an explicit 'Use when' clause exists.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with LeanData data' surfaces the natural product name 'LeanData' as a keyword, but it is the only meaningful trigger and misses common variations or task-oriented phrases (leads, routing, matching). It fits 'Some relevant keywords but missing common variations or synonyms' and is not a 4 because coverage is thin.	3 / 5
Distinctiveness Conflict Risk	Centering on the named product 'LeanData' gives it a clear, mostly-distinct niche with minimal conflict risk, matching 'Mostly distinct; minor overlap risk.' It is not a 5 because the generic action wording ('Manage data, records, and automate workflows') leaves some overlap risk with general data-management 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/leandata/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.