C

aeroleads-automation

by ComposioHQ

aeroleads-automation helps agents run Aeroleads lead research through Composio Rube MCP by discovering current tool schemas first, checking the Aeroleads connection, and executing workflows with verified inputs.

Stars67.4k
Favorites0
Comments0
AddedJul 11, 2026
CategoryLead Research
Install Command
npx skills add ComposioHQ/awesome-claude-skills --skill aeroleads-automation
Curation Score

This skill scores 68/100, which means it is acceptable for directory listing but limited. Directory users get enough information to understand when to use it and how an agent should start Aeroleads automation through Rube MCP, but the listing should be framed as a lightweight connector workflow rather than a fully documented, standalone automation package.

68/100
Strengths
  • Valid skill frontmatter clearly names the MCP requirement (`rube`) and describes the trigger: automating Aeroleads tasks via Rube MCP.
  • Prerequisites and setup steps explain how to connect Rube MCP, manage the Aeroleads connection, and confirm ACTIVE status before workflows.
  • The skill gives a repeatable discovery-first pattern using `RUBE_SEARCH_TOOLS`, which should reduce schema guesswork compared with a generic prompt.
Cautions
  • Execution depends on an active external Rube MCP and Aeroleads connection; the repository provides no local scripts or support files to validate behavior independently.
  • The skill relies on dynamic tool discovery rather than documenting concrete Aeroleads operations or end-to-end examples, so users may still need to interpret returned schemas.
Overview

Overview of aeroleads-automation skill

What aeroleads-automation is for

The aeroleads-automation skill helps an AI agent run Aeroleads-related lead research workflows through Composio’s Rube MCP server. Instead of guessing Aeroleads API shapes from memory, the skill instructs the agent to discover current Rube tool schemas first, verify the Aeroleads connection, and then execute the available Aeroleads operations with the right inputs.

Best-fit users and jobs

This skill is most useful for sales operations teams, growth researchers, founders, and assistants who use Aeroleads for Lead Research and want Claude or another MCP-capable agent to help with repeatable tasks. Good use cases include finding prospect contact data, enriching lead lists, checking available Aeroleads actions, and turning a targeting request into an executable tool workflow.

Main differentiator

The key value of aeroleads-automation is its “search tools first” discipline. Aeroleads and Composio tool schemas can change, so the skill does not hard-code a single workflow. It tells the agent to call RUBE_SEARCH_TOOLS before acting, which reduces broken calls, missing required fields, and outdated assumptions.

Adoption considerations

This is not a standalone scraper or local automation script. It requires Rube MCP to be configured and an active Aeroleads connection through Composio. If your AI client cannot use MCP tools, or if you do not have Aeroleads access, installing the aeroleads-automation skill will not produce useful results by itself.

How to Use aeroleads-automation skill

aeroleads-automation install context

Install from the Composio skills repository with:

npx skills add ComposioHQ/awesome-claude-skills --skill aeroleads-automation

Then add https://rube.app/mcp as an MCP server in your client configuration. The skill expects the Rube MCP tools to be available, especially RUBE_SEARCH_TOOLS and the connection-management tool for Aeroleads. Before trying real lead work, ask the agent to confirm that Rube responds and that the Aeroleads toolkit connection is ACTIVE.

Inputs the skill needs

For reliable aeroleads-automation usage, give the agent a specific lead research objective, not a vague request. Include target company types, roles, geography, exclusions, desired fields, volume limits, and how you want uncertain matches handled.

Weak prompt:

Find me leads for SaaS companies.

Stronger prompt:

Use aeroleads-automation for Lead Research. Find up to 50 VP Sales or Head of Revenue contacts at B2B SaaS companies in the US with 50-500 employees. Prefer companies selling to mid-market customers. Return name, title, company, LinkedIn URL if available, email if available, source/tool used, and confidence notes. First discover the current Aeroleads tools through Rube before executing.

This gives the agent enough constraints to select tools, avoid irrelevant prospects, and format the output for review.

Practical workflow to follow

A good aeroleads-automation guide workflow is:

  1. Ask the agent to call RUBE_SEARCH_TOOLS for the exact Aeroleads use case.
  2. Have it inspect returned tool slugs, required fields, limitations, and suggested execution plans.
  3. Confirm the Aeroleads connection with RUBE_MANAGE_CONNECTIONS using toolkit aeroleads.
  4. Run a small test query before requesting a large batch.
  5. Review match quality, then expand or refine the search.

This sequence matters because many failures come from skipping discovery, using stale parameter names, or running a broad query before the targeting criteria are clear.

Repository files to read first

The repository path is composio-skills/aeroleads-automation, and the important file is SKILL.md. Read it before installation if you need to verify the required MCP dependency, setup sequence, and tool discovery pattern. There are no extra scripts, rules, or reference folders in the current skill package, so the operating behavior is concentrated in that single file.

aeroleads-automation skill FAQ

Is aeroleads-automation enough without Aeroleads?

No. The skill is an agent instruction layer for using Aeroleads via Rube MCP. You still need an active Aeroleads connection through Composio. If the connection is not active, the agent should stop and guide you through the returned authentication link rather than attempting lead research.

How is this better than an ordinary prompt?

A normal prompt may ask the model to “find leads,” but it will not automatically know the current Rube MCP tool schemas. The aeroleads-automation skill explicitly requires tool discovery first, which is important for live integrations where available actions, field names, and validation rules can change.

Is it beginner-friendly?

It is beginner-friendly if your AI client already supports MCP and you are comfortable authorizing a SaaS connection. The setup is short, but the results still depend on clear search criteria. Beginners should start with small batches and ask the agent to explain each tool call before execution.

When should I not use it?

Do not use this skill for unsupported data collection, spam workflows, or bulk outreach without permission and compliance review. It is also a poor fit if you need a fully local workflow, custom scraping logic, or CRM-specific deduplication that is not available through the discovered Aeroleads/Rube tools.

How to Improve aeroleads-automation skill

Improve aeroleads-automation inputs

The fastest way to improve aeroleads-automation output is to tighten the lead definition. Add industry, company size, location, seniority, must-have titles, excluded titles, data fields, and maximum count. If you have example ideal customers, include them. If you have a “do not contact” list or existing CRM export, tell the agent to account for it before finalizing leads.

Watch common failure modes

Common issues include inactive Aeroleads connections, skipped RUBE_SEARCH_TOOLS discovery, overbroad lead criteria, missing required fields in tool calls, and unverified assumptions about what Aeroleads can return. A useful guardrail is to require the agent to summarize the discovered tool schema and planned call before taking action.

Iterate after the first output

Treat the first batch as calibration. Ask for a small result set, review false positives, then refine: “exclude agencies,” “only companies using Salesforce,” “prioritize director level and above,” or “separate founders from sales leaders.” Iteration improves precision more than asking for a large list immediately.

Strengthen the skill locally

If you maintain a local copy, consider adding examples for your common lead research motions, preferred output columns, compliance notes, and post-processing rules. The upstream skill is intentionally lightweight; organization-specific prompts can make it more dependable without changing the core requirement to discover current Rube Aeroleads tools first.

Ratings & Reviews

No ratings yet
Share your review
Sign in to leave a rating and comment for this skill.
G
0/10000
Latest reviews
Saving...