aeroleads
AeroLeads integration. Manage Leads, Persons, Organizations. Use when the user wants to interact with AeroLeads data.
61
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/aeroleads/SKILL.mdQuality
Discovery
67%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 adequately identifies the integration target (AeroLeads) and provides a 'Use when' clause, but the actions described are vague ('Manage') and the trigger terms lack common user-facing variations like 'contacts', 'prospects', or 'lead generation'. It's functional but could be significantly improved with more specific actions and richer trigger vocabulary.
Suggestions
Replace the vague 'Manage' with specific concrete actions like 'Create, search, update, and delete leads, persons, and organizations in AeroLeads'.
Add natural trigger terms users might say, such as 'contacts', 'prospects', 'lead generation', 'sales leads', or 'prospect lists' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AeroLeads) and some actions ('Manage Leads, Persons, Organizations'), but 'manage' is vague—it doesn't specify concrete actions like create, update, delete, search, or export. | 2 / 3 |
Completeness | Answers both 'what' (manage Leads, Persons, Organizations via AeroLeads integration) and 'when' ('Use when the user wants to interact with AeroLeads data'), though the 'when' clause is fairly generic. | 3 / 3 |
Trigger Term Quality | Includes 'AeroLeads', 'Leads', 'Persons', 'Organizations' which are relevant keywords, but misses common variations users might say like 'contacts', 'prospects', 'CRM', 'lead generation', or 'sales leads'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'AeroLeads' is distinctive and specific to that platform, but 'Manage Leads, Persons, Organizations' could overlap with other CRM or lead management skills (e.g., Salesforce, HubSpot integrations). | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid integration skill with excellent actionability and workflow clarity — every step has executable CLI commands and the connection state machine is well-documented with branching logic. The main weaknesses are moderate verbosity (introductory explanation, entity listing without context) and the lack of progressive disclosure structure for what is a fairly lengthy document.
Suggestions
Remove the introductory paragraph explaining what AeroLeads is — Claude already knows this and it wastes tokens.
Either remove the 'AeroLeads Overview' entity listing or make it actionable by linking each entity to specific action keys or example commands.
Consider splitting proxy request details and best practices into a separate reference file to keep the main SKILL.md focused on the core workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'AeroLeads is a prospecting tool that helps sales and marketing teams find email addresses...') and the overview section listing entities without actionable detail adds little value. The Membrane CLI instructions are reasonably efficient but could be tighter. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors), polling instructions, and conditional branching. The authentication flow includes a headless fallback path with clear steps. | 3 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections, but it's a fairly long monolithic document. The AeroLeads Overview section listing entities without linking to any detailed references feels like it should either be removed or linked to actionable content. No bundle files are referenced or provided. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- Reviewed
Table of Contents
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.