talenthr-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/talenthr-automation --openclawTalenthr Automation via Rube MCP
Automate Talenthr operations through Composio's Talenthr toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/talenthr
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Talenthr connection via
RUBE_MANAGE_CONNECTIONSwith toolkittalenthr - 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 toolkittalenthr - 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: "Talenthr 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 Talenthr task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["talenthr"]
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 Talenthr-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit talenthr |
| 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/talenthr-automation/SKILL.mdView on GitHub Overview
This skill automates Talenthr operations using Composio's Talenthr toolkit via Rube MCP. It emphasizes discovering current tool schemas before execution and requires an active Talenthr connection. The workflow follows discovering tools, verifying the connection, and then executing the chosen tool.
How This Skill Works
Technically, you first call RUBE_SEARCH_TOOLS to fetch available Talenthr tool slugs and schemas. Then you use RUBE_MANAGE_CONNECTIONS to ensure the talenthr toolkit connection is ACTIVE. Finally, you run RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and schema-compliant arguments, including memory and session_id.
When to Use It
- Setting up a new Talenthr automation workflow from scratch.
- Automating routine Talenthr operations using discovered tool slugs.
- Verifying updated tool schemas before execution after a schema change.
- Reusing a session ID across a multi-step Talenthr workflow.
- Diagnosing failures by confirming ACTIVE connection and handling pagination in tool lists.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify no API keys are required.
- Step 2: Run RUBE_SEARCH_TOOLS to confirm available Talenthr tools and their current schemas.
- Step 3: Use RUBE_MANAGE_CONNECTIONS to connect to the talenthr toolkit and then execute a tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current schemas before executing anything.
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before running 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 for new workflows and watch for pagination tokens.
Example Use Cases
- Onboard a new candidate by discovering the create_candidate tool from RUBE_SEARCH_TOOLS and executing it with the candidate data.
- Bulk update job postings by finding the bulk_update_jobs tool and running it with a list of changes using a shared session.
- Sync Talenthr task statuses to a dashboard by discovering the status_sync tool and invoking it with task IDs and status mappings.
- Archive completed Talenthr tasks by locating the archive_tasks tool and running it with a date filter.
- Validate tool schemas after an update by running RUBE_GET_TOOL_SCHEMAS and comparing to local expectations.
