What is required to start using smartrecruiters-automation?

Rube MCP must be connected and an active Smartrecruiters connection configured via the smartrecruiters toolkit; always run RUBE_SEARCH_TOOLS first to fetch current tool schemas.

How do I execute a tool?

Discover the tool with RUBE_SEARCH_TOOLS, verify the connection with RUBE_MANAGE_CONNECTIONS, then run the tool via RUBE_MULTI_EXECUTE_TOOL including memory and the session_id.

What are common pitfalls to avoid?

Hardcoding tool slugs or arguments, neglecting to call RUBE_SEARCH_TOOLS, forgetting the memory parameter in multi-execute calls, or running tools when the connection is not ACTIVE; always verify schemas and connection status.

smartrecruiters-automation

Scanned

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

Files (1)

SKILL.md

3.0 KB

Smartrecruiters Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/smartrecruiters

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["smartrecruiters"]
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 Smartrecruiters-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `smartrecruiters`
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/smartrecruiters-automation/SKILL.md

View on GitHub

Overview

This skill automates Smartrecruiters tasks by orchestrating tools from the Composio Smartrecruiters toolkit using the Rube MCP. It enforces discovering current tool schemas first to keep workflows up to date and resilient.

How This Skill Works

Set up the Rube MCP endpoint and connect to Smartrecruiters via the toolkit. Always call RUBE_SEARCH_TOOLS to fetch current tool schemas, then verify the connection with RUBE_MANAGE_CONNECTIONS before running tools. Execute discovered tools with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and the session_id to maintain context.

When to Use It

Automating a Smartrecruiters operation by selecting a tool slug discovered at runtime
Chaining steps in a workflow that requires reusing a session across actions
Ensuring tool schemas are current before invoking any tool
Performing bulk or multi-tool workflows via RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH
Validating the Smartrecruiters connection is ACTIVE before execution

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server; verify connectivity by calling RUBE_SEARCH_TOOLS
Step 2: Use RUBE_MANAGE_CONNECTIONS with toolkits: ["smartrecruiters"] and ensure the status is ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL with a memory payload and the correct session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and avoid hardcoding slugs or arguments
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools
Use exact field names and types from the search results for tool arguments
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}), to preserve state
Reuse session IDs within a workflow and paginate responses when needed

Example Use Cases

Discover a Smartrecruiters operation with RUBE_SEARCH_TOOLS, connect with RUBE_MANAGE_CONNECTIONS, and execute the tool via RUBE_MULTI_EXECUTE_TOOL to create a new job
Update a candidate status by selecting the appropriate tool slug from the search results and running it within an ACTIVE Smartrecruiters connection
Perform a bulk import of candidates using RUBE_REMOTE_WORKBENCH's run_composio_tool path with the discovered tool slug
Test connectivity and validate the Active status before running any workflow on Smartrecruiters
Handle a paginated tool result set by reissuing RUBE_SEARCH_TOOLS until no next-page tokens remain

Frequently Asked Questions

Add this skill to your agents