Lever Sandbox Automation

What This Skill Does

• This skill automates operations within a Lever Sandbox environment using Composio's Lever Sandbox toolkit and Rube MCP.
• It enables users to manage and test Lever configurations and workflows in a safe, isolated environment before deploying to production.
• This is useful for developers and administrators.

When to Use

• Discover available Lever Sandbox tools.
• Check the connection status to Lever Sandbox.
• Execute a specific Lever Sandbox tool.
• Automate testing of Lever configurations.
• Manage Lever Sandbox settings.
• Verify tool schemas before execution.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires an active Lever Sandbox connection.
• Emphasizes dynamic tool schema retrieval.
• Provides a structured workflow pattern.
• Includes connection status verification.
• Highlights common pitfalls and best practices.

Manual Installation

• Manual installation.
• View Full Skill Content.
• The complete markdown content that gets installed.
• Lever Sandbox Automation via Rube MCP.

Automate Lever Sandbox operations through Composio's Lever Sandbox toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/lever_sandbox

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Lever Sandbox connection via RUBE_MANAGE_CONNECTIONS with toolkit lever_sandbox 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 lever_sandbox 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: "Lever Sandbox 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 Lever Sandbox task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["lever_sandbox"] 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

Powered by Composio. Lever Sandbox Automation via Rube MCP

Automate Lever Sandbox operations through Composio's Lever Sandbox toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/lever_sandbox

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Lever Sandbox connection via RUBE_MANAGE_CONNECTIONS with toolkit lever_sandbox 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 lever_sandbox 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: "Lever Sandbox 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 Lever Sandbox task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["lever_sandbox"] 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

Powered by Composio