$ ~/registry/skill/composiohq-composio-skills-dropcontact-automation

SKILL

dropcontact-automation

Name: dropcontact-automation
Author: Composio

Automate Dropcontact contact enrichment and data tasks through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill itself is an open-source, prompt-only wrapper from a credible repository with strong community adoption, so the overall risk is low. However, its intended use is to drive Rube MCP/Composio and Dropcontact remote toolchains, so real-world use involves outbound connections and third-party account authorization that warrant attention to data egress and permission scope.

CredentialsCaution

The material says the skill itself needs 'no API keys,' but it explicitly requires an ACTIVE `dropcontact` connection via `RUBE_MANAGE_CONNECTIONS` and completing authentication through a returned auth link. This means credentials likely live in the Rube/Dropcontact side rather than in the skill itself. No explicit red flags of local secret harvesting or credential abuse are shown, but third-party connection authorization still warrants caution.

Network egressCaution

Although the top-level metadata lists no remote host, the README explicitly instructs users to add `https://rube.app/mcp` as an MCP server and references Composio/Dropcontact toolkit flows. This indicates real outbound traffic to Rube MCP and related third-party services, and task data may traverse that chain. That is a normal property of this type of integration, and no concrete red flag shows exfiltration to unrelated or unknown endpoints.

Code executionLow risk

The system marks this as prompt-only, and the material does not describe local install scripts, shell execution, process spawning, or elevated system capabilities. Its primary role is to instruct use of existing MCP tools. Therefore, for the skill itself, no local code-execution surface is evident.

Data accessCaution

The skill itself does not claim direct local file read/write access, but its purpose is to automate Dropcontact operations and it supports running remote workflows through `RUBE_MULTI_EXECUTE_TOOL`/`RUBE_REMOTE_WORKBENCH`. The practical data scope will depend on the permissions granted to the Dropcontact/Composio connection. No request for local data access beyond the stated function or excessive system permissions is shown.

Supply chainLow risk

The source is an open GitHub repository under ComposioHQ, the system marks it as open-source, and community adoption is high (64.7k stars). These are strong positive signals that reduce supply-chain risk. The license and maintenance status are not explicit in the provided material, which adds some uncertainty, but not enough to constitute a high-risk supply-chain red flag.

Recommendations

Only connect to `https://rube.app/mcp` when needed, and verify the authorization page is part of the legitimate Rube/Dropcontact flow.
Apply least privilege to the Dropcontact/Composio connection and avoid granting data scopes unrelated to the current task.
Review the tool list and parameters returned by `RUBE_SEARCH_TOOLS` before execution to avoid sending sensitive data to unnecessary remote tools.
Prefer reviewing the underlying open-source repository and recent commits to confirm the skill documentation still matches current Rube/Composio behavior.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "dropcontact-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/dropcontact-automation/SKILL.md
2. Save it as ~/.claude/skills/dropcontact-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Dropcontact Automation via Rube MCP

Automate Dropcontact operations through Composio's Dropcontact toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/dropcontact

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Dropcontact connection via RUBE_MANAGE_CONNECTIONS with toolkit dropcontact
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit dropcontact
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Dropcontact operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Dropcontact task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["dropcontact"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Dropcontact-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `dropcontact`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Automate Mailcoach email marketing and subscriber workflows through Rube MCP.

ComposioGet→

$ loading_