async-interview-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/async-interview-automation --openclawAsync Interview Automation via Rube MCP
Automate Async Interview operations through Composio's Async Interview toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/async_interview
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Async Interview connection via
RUBE_MANAGE_CONNECTIONSwith toolkitasync_interview - 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 toolkitasync_interview - 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: "Async Interview 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 Async Interview task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["async_interview"]
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 Async Interview-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit async_interview |
| 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/async-interview-automation/SKILL.mdView on GitHub Overview
Automate Async Interview operations through Composio's Async Interview toolkit via Rube MCP. This skill emphasizes always searching for current tool schemas before running workflows, and it requires a connected Rube MCP and an ACTIVE Async Interview connection.
How This Skill Works
You first discover available tools using RUBE_SEARCH_TOOLS to obtain up-to-date slugs and input schemas. Then you verify or establish a connection with RUBE_MANAGE_CONNECTIONS for the async_interview toolkit. Finally, you execute the selected tool(s) with RUBE_MULTI_EXECUTE_TOOL, providing the discovered arguments, a memory object, and the current session_id to maintain context.
When to Use It
- Automating a sequence of Async Interview tasks across multiple tools.
- When tool schemas change frequently and you must fetch current slugs and arguments via RUBE_SEARCH_TOOLS.
- Before running workflows, ensure RUBE_MANAGE_CONNECTIONS reports an ACTIVE Async Interview connection.
- Reusing session IDs within a workflow to maintain context.
- Performing bulk operations that orchestrate several tools with RUBE_MULTI_EXECUTE_TOOL.
Quick Start
- Step 1: Verify Rube MCP is available by calling RUBE_SEARCH_TOOLS.
- Step 2: Connect with RUBE_MANAGE_CONNECTIONS for the async_interview toolkit and ensure the status is ACTIVE.
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper arguments, memory, and the current session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get up-to-date tool schemas.
- Check that the connection status is ACTIVE before executing any tools.
- Use exact field names/types from the tool schemas; avoid hardcoding slugs.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs for related tasks and generate new ones for new workflows.
Example Use Cases
- Automate a candidate screening flow by discovering tools, connecting, and executing screening steps in sequence.
- Update candidate status across tools after each interview stage to keep records synchronized.
- Run multiple async-interview tasks in a single session using RUBE_MULTI_EXECUTE_TOOL for efficiency.
- Handle tool schema changes by re-fetching schemas with RUBE_SEARCH_TOOLS instead of hardcoding values.
- Orchestrate a batch of tool invocations via RUBE_REMOTE_WORKBENCH run_composio_tool for bulk operations.
