icims-talent-cloud-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/icims-talent-cloud-automation --openclawIcims Talent Cloud Automation via Rube MCP
Automate Icims Talent Cloud operations through Composio's Icims Talent Cloud toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/icims_talent_cloud
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Icims Talent Cloud connection via
RUBE_MANAGE_CONNECTIONSwith toolkiticims_talent_cloud - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkiticims_talent_cloud - 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: "Icims Talent Cloud 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 Icims Talent Cloud task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["icims_talent_cloud"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Icims Talent Cloud-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit icims_talent_cloud |
| 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/icims-talent-cloud-automation/SKILL.mdView on GitHub Overview
Automate Icims Talent Cloud operations using Composio's Icims Talent Cloud toolkit via Rube MCP. The workflow emphasizes discovering current tool schemas before each run and ensuring an active connection, so tasks stay aligned with the latest tool definitions. This enables reliable, scalable automation of Icims tasks.
How This Skill Works
Connect Rube MCP and confirm an active Icims Talent Cloud connection via the icims_talent_cloud toolkit. Always call RUBE_SEARCH_TOOLS to fetch current tool schemas, then discover the target tool, verify the connection, and execute with RUBE_MULTI_EXECUTE_TOOL, including memory in every call.
When to Use It
- Automating repetitive Icims Talent Cloud tasks by using tool discovery to fetch latest slugs and schemas
- When starting a new Icims workflow, discover tools first to adapt to schema changes
- Before running bulk operations, verify the Active connection via RUBE_MANAGE_CONNECTIONS
- Integrating Icims tasks into larger automation pipelines where tool schemas can change
- Troubleshooting workflow issues by listing available tools and schemas from RUBE_SEARCH_TOOLS
Quick Start
- Step 1: Add Rube MCP endpoint to your client configuration: https://rube.app/mcp
- Step 2: Run RUBE_SEARCH_TOOLS with use_case Icims Talent Cloud operations to retrieve current tool schemas
- Step 3: Ensure ACTIVE connection via RUBE_MANAGE_CONNECTIONS and run a discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory
Best Practices
- Always search first with RUBE_SEARCH_TOOLS to fetch current schemas
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
- Use exact field names and types from search results
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls
- Reuse session IDs within a workflow and handle pagination tokens
Example Use Cases
- Discover tools for Icims Talent Cloud operations and pick a tool slug to automate candidate creation
- Activate and verify the Icims connection, then run a tool to update candidate status
- Execute a tool with arguments strictly matching the discovered schema
- Bulk save a set of changes across multiple candidates using a single session
- Iterate over paginated tool results to fetch all available operations