Name: leadiq
Rating: 60.8 (1 reviews)
Author: membranedev

leadiq

LeadIQ integration. Manage Leads, Persons, Organizations, Accounts, Activities, Notes and more. Use when the user wants to interact with LeadIQ data.

Quality

71%

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/leadiq/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 body is highly actionable with copy-paste CLI commands and a well-sequenced connection state machine, and it stays mostly concise. Its main gaps are a missing explicit validate-retry loop for the client-action recovery path and a modest amount of inlined reference material that could live in separate files.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste CLI commands and tight tables, though a few lines over-explain Claude-likely context (the LinkedIn prospecting intro and 'This will burn less tokens and make communication more secure'), fitting 'efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests with concrete flag tables covering the common cases, matching the top anchor.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-machine branches (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-loop checkpoint, but it lacks an explicit validate-fix-retry feedback loop for the auth/client-action path, fitting 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	Content is well organized into logical sections with a 'Popular actions' table keeping bulk enumeration out of the prose and no nested references (no bundle files exist), but some reference-style material (proxy flag table, clientAction schema) is inlined rather than split, fitting 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	17 / 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 is distinctive and provides an explicit 'Use when' trigger plus a clear (if generic) 'what', but its capability language is thin — a single 'Manage' verb over a noun list rather than concrete operations. Tightening the action verbs would lift the specificity dimension.

Suggestions

Replace the single generic verb 'Manage' with 2-3 concrete actions users perform (e.g. 'Search for leads, capture contact info, submit person feedback').

Add natural trigger synonyms beyond 'LeadIQ data' (e.g. 'prospecting', 'find contact info', 'build lead lists') so the description matches what users actually say.

Keep the explicit 'Use when...' clause but broaden it to cover the prospecting/outreach use cases implied by the body.

Dimension	Reasoning	Score
Specificity	It names the domain (LeadIQ) and lists entities ('Manage Leads, Persons, Organizations, Accounts, Activities, Notes and more') but the action verb is the single generic 'Manage' with no concrete operations, fitting the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states a clear 'what' ('LeadIQ integration. Manage Leads, Persons...') and an explicit 'when' ('Use when the user wants to interact with LeadIQ data'); the 'when' is concrete but somewhat narrow, matching 'has both what and when; when could be more explicit or specific'.	4 / 5
Trigger Term Quality	It surfaces domain nouns ('Leads', 'Persons', 'Organizations') a user might mention and a reasonable trigger phrase ('Use when the user wants to interact with LeadIQ data'), but lacks common synonyms or variations beyond 'LeadIQ data', placing it at 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The LeadIQ product name plus its specific entities form a clear niche with distinct triggers and minimal conflict risk against other skills, matching the top anchor.	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/leadiq/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.