Name: leadsquared
Rating: 60 (1 reviews)
Author: membranedev

leadsquared

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

Quality

70%

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

Quality

Content

73%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 executable CLI commands and a well-structured connection workflow. It loses points for restating product background Claude already knows and for lacking validation checkpoints around action execution and proxy requests.

Suggestions

Trim the opening paragraph that explains what LeadSquared and marketing automation are; assume Claude's domain knowledge.

Add a validation/verification step after running actions or proxy requests (e.g. inspect the `output` field and check for error states before proceeding on batch operations).

Consider moving the full proxy flag reference table into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph restates what LeadSquared is ('marketing automation and CRM software...') — context Claude already knows — and a few sections could be tightened.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (membrane login, connection ensure, action list/run, request with a full flag table), covering the common cases with real syntax and JSON-output flags.	5 / 5
Workflow Clarity	The connection setup is clearly sequenced with a polling loop and explicit state-by-state branches (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but there are no validation checkpoints after running actions or proxy requests, which are the destructive/batch-prone steps.	4 / 5
Progressive Disclosure	Content is organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no bundle files to offload to; structure is good, though a few inline reference-like sections (the full proxy flag table) could live in a separate reference.	4 / 5
	Total	16 / 20 Passed

Description

66%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 well-targeted to a distinct named product and includes both a 'what' and an explicit 'Use when' trigger. Its main weakness is generic action language ('manage data, records') rather than concrete capabilities.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'create and update leads, log activities, manage tasks, and automate marketing workflows'.

Broaden trigger terms with natural phrasings users might say, such as 'leads', 'lead activities', or 'LeadSquared CRM'.

Dimension	Reasoning	Score
Specificity	The description names the LeadSquared domain and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete capabilities, so coverage is not comprehensive.	3 / 5
Completeness	It answers both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with LeadSquared data') explicitly, though the 'what' could be more specific.	4 / 5
Trigger Term Quality	It includes the natural term 'interact with LeadSquared data' and the product name, but lacks common synonyms or variations a user might actually say, leaving keyword coverage incomplete.	3 / 5
Distinctiveness Conflict Risk	LeadSquared is a specific named product, giving the skill a clear niche with distinct triggers and minimal risk of firing for unrelated skills.	5 / 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/leadsquared/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.