home / skills / composiohq / awesome-claude-skills / async-interview-automation

async-interview-automation skill

safe

/async-interview-automation

This skill automates Async Interview tasks through Rube MCP, always discovering current tool schemas before execution to ensure accurate automation.

npx playbooks add skill composiohq/awesome-claude-skills --skill async-interview-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

3.0 KB

---
name: async-interview-automation
description: "Automate Async Interview tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# 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](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `async_interview`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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

| 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](https://composio.dev)*

Overview

This skill automates Async Interview tasks using Composio's Async Interview toolkit via the Rube MCP gateway. It provides a repeatable pattern for discovering tools, validating connections, and executing multi-step operations while enforcing schema compliance and session management. Use it to integrate composio-powered interview workflows into automation pipelines.

How this skill works

The skill first queries RUBE_SEARCH_TOOLS to discover current tool slugs, input schemas, and execution recommendations. It ensures an ACTIVE connection via RUBE_MANAGE_CONNECTIONS for the async_interview toolkit and then runs one or more tools with RUBE_MULTI_EXECUTE_TOOL, always including a memory object and reusing a session ID. It also supports fetching full schemas and handling pagination where responses are paginated.

When to use it

Automating candidate screening, asynchronous interview scheduling, or question delivery at scale
Embedding composio Async Interview capabilities into CI/CD or HR automation pipelines
Building agents that must adapt dynamically to changing tool schemas
Running bulk operations or remote batches with run_composio_tool() via RUBE_REMOTE_WORKBENCH
When you need strict schema compliance and session-based multi-step workflows

Best practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and exact input schemas
Check RUBE_MANAGE_CONNECTIONS and ensure toolkit async_interview is ACTIVE before execution
Include a memory object (even if empty) in RUBE_MULTI_EXECUTE_TOOL calls and reuse session IDs within a workflow
Avoid hardcoding tool slugs or field names; use RUBE_GET_TOOL_SCHEMAS when schemaRef is provided
Handle pagination tokens in responses and continue fetching until results are complete

Example use cases

Discover interview question delivery and scoring tools, then run them in sequence to process candidate responses
Set up a recurring workflow that generates and distributes interview assignments asynchronously to candidates
Bulk import candidate data and run batch grading or transcript generation via RUBE_REMOTE_WORKBENCH
Integrate Async Interview outputs into an HR dashboard by fetching tool schemas and mapping results to your data model
Create an agent that adapts to new toolkit fields by searching for tools at runtime and adjusting arguments

FAQ

Do I need API keys to use Rube MCP?

No API keys are required; add https://rube.app/mcp as an MCP server in your client and call the RUBE endpoints.

What should I do if a tool schema changes mid-workflow?

Re-run RUBE_SEARCH_TOOLS to get updated schemas, adjust arguments to match exact field names and types, and restart the workflow with a new session ID if necessary.