Automate Aeroleads tasks via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:haniakrim21/everything-claude-code --skill aeroleads-automation73
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 96%
↑ 1.84xAgent success when using this skill
Validation for skill structure
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too vague to effectively guide skill selection. It names the integration (Aeroleads via Composio) but fails to describe what specific tasks can be automated or when Claude should choose this skill. The operational instruction about searching tools first doesn't help with skill selection.
Suggestions
Add specific capabilities like 'Find business emails, extract LinkedIn profiles, build prospect lists, enrich contact data'
Add a 'Use when...' clause with trigger terms like 'lead generation', 'find emails', 'prospect research', 'Aeroleads', 'contact enrichment'
Remove or relocate the operational instruction ('Always search tools first') as it doesn't help with skill selection
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate Aeroleads tasks' without specifying what concrete actions are possible. No specific capabilities like 'extract leads', 'enrich contacts', or 'export data' are mentioned. | 1 / 3 |
Completeness | The 'what' is extremely vague ('Automate Aeroleads tasks') and there is no 'Use when...' clause or explicit trigger guidance. The instruction to 'search tools first' is operational guidance, not a usage trigger. | 1 / 3 |
Trigger Term Quality | Includes 'Aeroleads' as a specific product name which is a relevant keyword, but lacks natural variations users might say like 'lead generation', 'prospect finder', 'email finder', or common use case terms. | 2 / 3 |
Distinctiveness Conflict Risk | 'Aeroleads' is a specific product name which helps distinguish it, but 'Automate tasks via Rube MCP (Composio)' pattern could conflict with other Composio-based skills. The lack of specific actions makes overlap more likely. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently teaches Claude how to automate Aeroleads tasks via Rube MCP. It excels in providing concrete, executable patterns while maintaining brevity. The workflow is clearly sequenced with appropriate validation steps, and the Known Pitfalls section adds valuable guardrails.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic concepts. Every section serves a purpose with no padding or unnecessary context about what Aeroleads or Composio are. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready tool invocation patterns with specific parameter structures. The workflow steps show exact tool names and argument formats that Claude can execute directly. | 3 / 3 |
Workflow Clarity | Clear 3-step workflow pattern (Discover → Check Connection → Execute) with explicit validation checkpoint (verify ACTIVE status before proceeding). The Known Pitfalls section provides error prevention guidance. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from prerequisites to setup to core workflow. External reference to toolkit docs is one level deep and clearly signaled. Quick reference table provides efficient navigation. | 3 / 3 |
Total | 12 / 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 | |
Table of Contents
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.