aeroleads
AeroLeads integration. Manage Leads, Persons, Organizations. Use when the user wants to interact with AeroLeads data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill aeroleads75
Quality
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/aeroleads/SKILL.mdDiscovery
75%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 and provides explicit 'Use when' guidance, making it functional for skill selection. However, it lacks specific action verbs and could benefit from more natural trigger terms that users might actually say when needing lead management functionality.
Suggestions
Add specific concrete actions like 'create leads, search contacts, update organizations, export prospect data' to improve specificity.
Include common user trigger terms like 'contacts', 'prospects', 'CRM', 'sales leads', or 'lead database' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AeroLeads) and mentions general actions ('Manage Leads, Persons, Organizations'), but lacks specific concrete actions like 'create leads', 'search contacts', 'export data', or 'sync organizations'. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage Leads, Persons, Organizations') and when ('Use when the user wants to interact with AeroLeads data'), providing clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'AeroLeads', 'Leads', 'Persons', 'Organizations' which are relevant, but misses common variations users might say like 'contacts', 'prospects', 'CRM', 'sales leads', or 'lead management'. | 2 / 3 |
Distinctiveness Conflict Risk | The explicit mention of 'AeroLeads' as a specific integration creates a clear niche that is unlikely to conflict with other CRM or lead management skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid actionable CLI commands for AeroLeads integration via Membrane, with good coverage of common operations and proxy requests. However, it includes unnecessary introductory content about what AeroLeads is, and the entity overview section provides no actionable value. The workflow lacks validation checkpoints and error recovery guidance.
Suggestions
Remove the introductory paragraph explaining what AeroLeads is and the bullet-point overview of entities - Claude doesn't need this context
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep CONNECTION_ID')
Include error handling guidance for common failure scenarios (authentication failures, rate limits, invalid action IDs)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'AeroLeads is a prospecting tool that helps sales and marketing teams...') that Claude already knows. The overview section listing entities without actionable context adds little value. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including connection setup, action discovery, action execution with parameters, and proxy requests with comprehensive flag documentation. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection, but lacks explicit validation checkpoints. No feedback loops for error recovery (e.g., what to do if connection fails, how to verify successful authentication). | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the 'AeroLeads Overview' bullet list adds no value and could be removed. No references to external detailed documentation for advanced use cases. | 2 / 3 |
Total | 9 / 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 | |
- 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.