What should I do before running Deel workflows?

Ensure RUBE_SEARCH_TOOLS responds with current tool slugs and that RUBE_MANAGE_CONNECTIONS shows ACTIVE for the Deel toolkit; then run RUBE_MULTI_EXECUTE_TOOL with the correct memory payload.

How do I handle changing tool schemas?

Always run RUBE_SEARCH_TOOLS to fetch the latest schemas and avoid hardcoding slugs or arguments.

How do I manage sessions across tasks?

Reuse session IDs within a workflow and generate new ones for new workflows; include session_id in each step.

deel-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/deel-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Deel Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/deel

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["deel"]
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 Deel-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `deel`
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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/deel-automation/SKILL.mdView on GitHub

Overview

Automate Deel operations through Composio's Deel toolkit using Rube MCP. The workflow emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, ensuring an ACTIVE Deel connection, and executing tools with a memory payload to support session reuse.

How This Skill Works

First, query RUBE_SEARCH_TOOLS to retrieve available Deel tool slugs and input schemas. Then verify the Deel connection is ACTIVE via RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing the schema-compliant arguments, a memory payload, and your session_id.

When to Use It

You want to automate a Deel task without custom coding, using live tool schemas.
Tool schemas change and you need the latest slugs and input fields before running workflows.
You need to run multiple Deel tasks in a bulk or sequential workflow.
You want to reuse a single session across related Deel tasks to maintain context.
You must verify the Deel connection is ACTIVE before executing any Deel tool.

Quick Start

Step 1: RUBE_SEARCH_TOOLS queries: [{use_case: 'Deel operations'}] to discover available Deel tools and schemas.
Step 2: RUBE_MANAGE_CONNECTIONS toolkits: ['deel']; session_id: 'your_session_id' and ensure ACTIVE.
Step 3: RUBE_MULTI_EXECUTE_TOOL with tool_slug from search results, proper arguments, memory: {} , and your_session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to capture current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
Use exact field names and types from the search results; avoid hardcoding slugs.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow; generate new ones when starting a new workflow.

Example Use Cases

Automate creating a Deel contract for a new contractor by selecting the appropriate tool slug from RUBE_SEARCH_TOOLS and supplying required fields.
Update an existing Deel contract's terms or status based on HR updates, using the discovered tool and schema.
Fetch Deel contract details to sync with an external CRM or payroll system.
Run a bulk Deel workflow to generate contracts for a batch of contractors in one orchestration.
Retrieve the latest Deel payment terms and reflect them in a dashboards or reporting tool.

Frequently Asked Questions

Add this skill to your agents