What is Recruitee Automation via Rube MCP?

It’s a workflow pattern that automates Recruitee operations using Composio’s Recruitee toolkit through the Rube MCP bridge, requiring current tool schemas and an ACTIVE connection.

Do I need API keys to use this skill?

No API keys are needed. You add the Rube MCP endpoint (https://rube.app/mcp) in your client configuration and rely on tool schemas retrieved by RUBE_SEARCH_TOOLS.

What if tool schemas change?

Always run RUBE_SEARCH_TOOLS first to get up-to-date slugs and arguments; do not hardcode tool slugs or field names, and include memory in every RUBE_MULTI_EXECUTE_TOOL call.

recruitee-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Recruitee Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/recruitee

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["recruitee"]
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 Recruitee-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `recruitee`
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/recruitee-automation/SKILL.mdView on GitHub

Overview

Automates Recruitee operations through Composio's Recruitee toolkit via Rube MCP. It emphasizes discovering tool schemas first and ensuring an active connection before workflow execution.

How This Skill Works

Technically, you first discover available Recruitee tools via RUBE_SEARCH_TOOLS to fetch current slugs and schemas. Then you verify the Recruitee connection with RUBE_MANAGE_CONNECTIONS and ensure the session is ACTIVE. Finally, you execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing the discovered slug, exact arguments from the schema, and a memory object (even if empty).

When to Use It

Automate routine Recruitee tasks (e.g., posting jobs, updating candidates)
Orchestrate multi-step workflows across tools using discovered schemas
Set up a new Recruitee integration and verify an ACTIVE connection
Ensure tool schemas are current by re-searching tools before execution
Handle session-based workflows with proper session reuse and pagination awareness

Quick Start

Step 1: Verify RUBE_SEARCH_TOOLS is available and returns Recruitee tool slugs
Step 2: Call RUBE_MANAGE_CONNECTIONS for toolkit recruitee and ensure ACTIVE
Step 3: Discover a tool with RUBE_SEARCH_TOOLS and run it via RUBE_MULTI_EXECUTE_TOOL using the required memory and schema fields

Best Practices

Always call RUBE_SEARCH_TOOLS before running any workflow to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Use exact field names and types from search results; do not hardcode slugs or args
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs for related steps; generate new sessions only for new workflows

Example Use Cases

Discover a Recruitee tool for creating a new job posting and execute it with the required job fields
Fetch candidate management tools, connect to Recruitee, then move a candidate through stages in a single session
Bulk update statuses for multiple job postings across departments by executing discovered tools in sequence
Refresh the Recruitee connection and tool schemas when a schema change is detected, using RUBE_SEARCH_TOOLS first
Log execution results and memory state after each tool run for auditing and rollback planning

Frequently Asked Questions

Add this skill to your agents