Async Interview Automation

What This Skill Does

• This skill automates interactions with the Async Interview platform through Composio's Rube MCP.
• It allows users to programmatically manage and analyze asynchronous video interviews.
• This is helpful for recruiters and HR professionals looking to streamline their hiring process.

When to Use

• Schedule and send interview invitations.
• Retrieve candidate responses.
• Analyze interview performance.
• Automate candidate screening.
• Integrate interview data into HR systems.
• Manage interview workflows programmatically.

Key Features

• Automates Async Interview operations.
• Uses Rube MCP for tool management.
• Discovers available tools via RUBE_SEARCH_TOOLS.
• Checks connection status before execution.
• Enforces schema compliance for arguments.
• Provides a structured workflow pattern.

Manual Installation

Manual installation View Full Skill Content The complete markdown content that gets installed Async 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_CONNECTIONS with toolkit async_interview 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 async_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_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