Name: leadboxer
Rating: 62.4 (1 reviews)
Author: membranedev

leadboxer

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

Quality

73%

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

Quality

Content

68%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 skill is highly actionable with copy-paste Membrane CLI commands and a strong connection-setup workflow, but it loses points for an unnecessary intro paragraph and missing validation checkpoints around destructive action execution.

Suggestions

Trim or remove the background paragraph ("LeadBoxer is a B2B website visitor tracking...") and the flat entity list, which add tokens without actionable value.

Add a verification step before/after destructive actions (e.g., confirm the target lead/segment ID and check the `output` field for success before considering the operation complete).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening paragraph explaining what LeadBoxer is and the flat entity list are unnecessary context-padding Claude does not need.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands covering the common cases (install, login, connection ensure/get, action list/run, request) plus a concrete flags table and popular-action keys.	5 / 5
Workflow Clarity	The connection setup has explicit state-check validation and error recovery, but running actions and proxy requests for destructive operations (delete-segment, update-lead-tags) lack verification checkpoints, capping this dimension.	3 / 5
Progressive Disclosure	Well-organized single-file structure with clear section headers and no nested or buried references; minor gaps only, with the popular-actions and proxy-options tables reasonably kept inline.	4 / 5
	Total	15 / 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 description that names the product, enumerates specific managed entities, and includes an explicit 'Use when' trigger. It falls short of top marks mainly because the action verbs are uniform and the trigger phrase is generic.

Suggestions

Vary the action verbs beyond 'Manage' to reflect distinct capabilities (e.g., 'Create and update leads, search organizations, log activities, assign deals').

Make the 'Use when' clause more concrete by listing trigger tasks (e.g., 'Use when the user wants to track website visitors, qualify leads, look up organizations by domain, or manage LeadBoxer segments').

Dimension	Reasoning	Score
Specificity	Lists several specific entities ("Leads, Persons, Organizations, Deals, Activities, Notes") under one action verb ("Manage"), giving good concrete coverage but not the varied multi-action breadth of the anchor-5 example.	4 / 5
Completeness	Answers both "what" ("Manage Leads, Persons...") and "when" ("Use when the user wants to interact with LeadBoxer data"), but the trigger is generic compared to anchor 5's concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the product name "LeadBoxer" plus natural entity terms ("Leads", "Organizations", "Deals"); good keyword coverage, though few synonyms exist for this niche product.	4 / 5
Distinctiveness Conflict Risk	Targets a named niche product ("LeadBoxer") with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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/leadboxer/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.