Name: helloleads
Rating: 64.8 (1 reviews)
Author: membranedev

helloleads

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

Quality

77%

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/helloleads/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.

A highly actionable, command-centric skill body with strong executable examples and clear sequencing. Its main gaps are missing validation/verification steps around data-mutating actions and some redundancy across the action-discovery sections.

Suggestions

Add explicit verification steps after connect and action run (e.g., check the JSON output for expected fields or errors before proceeding) to support destructive/batch operations.

Consolidate the overlapping 'Popular actions', 'Searching for actions', and 'Running actions' sections to remove redundancy and tighten the flow.

Trim the introductory 'HelloLeads is a CRM...' paragraph and the rationale clauses in 'Best practices' since Claude can infer this context.

Dimension	Reasoning	Score
Conciseness	Mostly lean and command-driven with only minor over-explanation (the introductory 'HelloLeads is a CRM...' paragraph and the rationale clauses in 'Best practices') that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready npx commands for login, connect, connection list, action list, action run, and proxy requests, plus a comprehensive flag table covering the common cases.	5 / 5
Workflow Clarity	The setup → connect → discover → run sequence is clearly numbered, but there are no validation or verification checkpoints for data-mutating operations, which caps this dimension per the batch/destructive rule.	3 / 5
Progressive Disclosure	Well-organized into clear headed sections in a single file with no bundle files to reference; minor redundancy between 'Popular actions', 'Searching for actions', and 'Running actions' keeps it just short of ideal.	4 / 5
	Total	16 / 20 Passed

Description

78%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.

A solid, third-person description that names the product and enumerates concrete CRM entities with an explicit 'Use when' trigger. The main weakness is the generic 'Manage' verb and a slightly broad 'when' clause.

Suggestions

Replace the generic 'Manage' with more concrete verbs (e.g., 'Create, update, and search Leads, Persons, Organizations, Deals, Activities, and Notes') to lift specificity.

Tighten the 'when' clause with concrete trigger phrases, e.g., 'Use when the user wants to create or update leads, manage deals, or query HelloLeads CRM data.'

Drop 'and more' or replace it with the remaining entity types so coverage reads as comprehensive rather than open-ended.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities ('Manage Leads, Persons, Organizations, Deals, Activities, Notes') but relies on a single generic verb ('Manage') and trails off with 'and more', leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' (manage the listed entities) and 'when' ('Use when the user wants to interact with HelloLeads data'), but the 'when' trigger is somewhat generic and could be more specific.	4 / 5
Trigger Term Quality	Good keyword coverage via the product name and the enumerated CRM entity types users would naturally mention, though a few natural synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The named product 'HelloLeads' plus its specific entity vocabulary gives it a clear niche with minimal risk of triggering for the wrong skill.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: membranedev/application-skills
Path: skills/helloleads/SKILL.md
Commit: f484c82

Reviewed: ~21 hours 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.