Name: leadgenius
Rating: 61.6 (1 reviews)
Author: membranedev

leadgenius

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

Quality

72%

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/leadgenius/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 comprehensive, executable CLI commands and a well-sequenced connection workflow that includes state-based validation. Its main weaknesses are a few minor conciseness lapses, broken cross-references in the step numbering, and content that could be split into reference files for a skill of this length.

Suggestions

Fix the dangling "skip to Step 2" reference and the "1b" heading (no matching "1a") by introducing consistent step labels so the workflow sequence is unambiguous.

Trim the introductory product description and editorial phrases like "so you can focus on the integration logic rather than auth plumbing" to tighten conciseness.

Consider moving the detailed clientAction state map and the proxy flag table into a separate reference file (e.g. REFERENCE.md) to improve progressive disclosure for a skill over 50 lines.

Dimension	Reasoning	Score
Conciseness	The body is command-driven and lean with minimal padding, though the opening product description ("LeadGenius is a B2B data provider...") and phrases like "so you can focus on the integration logic rather than auth plumbing" are minor over-explanation that could be trimmed, matching the efficient-with-minor-instances anchor.	4 / 5
Actionability	It provides copy-paste-ready executable commands across install, login, connection ensure, action list/run with JSON input, and proxy requests, plus a full flag-options table, covering the common cases fully per the anchor.	5 / 5
Workflow Clarity	The connect-to-run sequence has explicit validation checkpoints (polling --wait, READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR state handling, re-poll after user action), but the dangling "skip to Step 2" reference and a "1b" heading with no "1a" are minor navigation gaps, matching the clear-sequence-with-minor-gaps anchor.	4 / 5
Progressive Disclosure	With no bundle files present, all content is inline but well-organized under clear section headers (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices); the ~140-line length exceeds the simple-skill exception, and some material like the clientAction state map could live in a separate file, matching the good-structure-with-minor-gaps anchor.	4 / 5
	Total	17 / 20 Passed

Description

62%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 uses proper third-person voice and includes an explicit "Use when" trigger, giving it solid completeness and distinctiveness. It is held back by generic action verbs and a lack of natural trigger synonyms, leaving specificity and trigger-term quality in the mid-range.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete LeadGenius actions such as "build lead lists, enrich contact records, and automate outreach workflows" to raise specificity.

Expand the "Use when" clause with natural trigger phrases users would say, e.g. "Use when the user wants to build lead lists, enrich contacts, or automate outreach in LeadGenius."

Add common synonyms or surface terms (e.g. "leads," "prospecting," "B2B contacts") so the description matches how users actually phrase the request.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the LeadGenius domain plus a couple of actions, but the actions are generic (manage/automate) rather than concrete like "extract," "fill," or "merge," matching the domain-plus-actions-but-not-comprehensive anchor.	3 / 5
Completeness	It states both the what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with LeadGenius data"), but the when is generic rather than listing concrete trigger phrases, matching the has-both-but-when-could-be-more-specific anchor.	4 / 5
Trigger Term Quality	The description surfaces "LeadGenius," "data," "records," and "workflows," but offers no synonyms, variations, or file extensions a user might naturally say, fitting the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The branded "LeadGenius integration" / "interact with LeadGenius data" framing gives it a clear niche with minimal conflict risk, though the generic action language leaves minor overlap with adjacent CRM/data skills, matching the mostly-distinct anchor.	4 / 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/leadgenius/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.