$ ~/registry/skill/composiohq-composio-skills-drip-jobs-automation

SKILL

drip-jobs-automation

Name: drip-jobs-automation
Author: Composio

Automate Drip Jobs recruiting queries and workflows 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 appears to be open-source, prompt/documentation-only content with no declared local code execution or direct environment-variable requirements, so overall risk is low. The main consideration is that it directs users to connect to a remote Rube MCP service and a Drip Jobs account, which introduces normal third-party data flow and account-authorization exposure.

CredentialsCaution

No local API key or environment variable is declared, but the material explicitly requires creating an active Drip Jobs connection via RUBE_MANAGE_CONNECTIONS and following an auth link if not active; this implies third-party account tokens/OAuth are involved, creating normal credential-grant and misuse exposure.

Network egressCaution

The README explicitly instructs adding https://rube.app/mcp as an MCP server and interacting with Drip Jobs through Composio/Rube; user inputs, task arguments, and results would therefore be sent to these declared remote services, with no evidence of unrelated or hidden exfiltration endpoints.

Code executionLow risk

Based on the material, this is a prompt/instructional skill with no executable code, install script, or local process-launch step; it only describes invoking remote MCP tools and does not request local system-level execution privileges.

Data accessCaution

There is no indication of reading local files, system directories, or host-sensitive resources; however, once connected to Drip Jobs, the skill is intended to automate actions in that account, so it can read/modify relevant remote business data as part of its normal functional scope.

Supply chainLow risk

The source is a public GitHub repository, marked as open-source, with strong community adoption (64.7k stars), all of which materially reduce supply-chain risk; the skill also appears to be primarily documentation/prompt content. The missing license declaration and unknown maintenance status are worth noting, but do not by themselves justify a high-risk rating.

Recommendations

Before connecting Rube MCP and Drip Jobs, confirm your organization permits sending relevant business data to rube.app/Composio for processing.
Use a least-privilege Drip Jobs account for authorization and regularly review/revoke connections that are no longer needed.
Validate the tools and parameter scope returned by RUBE_SEARCH_TOOLS on low-sensitivity or test data before running bulk operations.
Check recent repository activity, maintainer identity, and official Composio/Rube documentation to ensure the skill description is still current.

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 "drip-jobs-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/drip-jobs-automation/SKILL.md
2. Save it as ~/.claude/skills/drip-jobs-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Drip Jobs Automation via Rube MCP

Automate Drip Jobs operations through Composio's Drip Jobs toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/drip_jobs

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Drip Jobs connection via RUBE_MANAGE_CONNECTIONS with toolkit drip_jobs
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 drip_jobs
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: "Drip Jobs 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 Drip Jobs task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["drip_jobs"]
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 Drip Jobs-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `drip_jobs`
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 Dropcontact contact enrichment and data tasks through Rube MCP.

ComposioGet→

$ loading_