How do I ensure I am using current tool schemas?

Always call RUBE_SEARCH_TOOLS before executing any tool to fetch the latest tool slugs and input schemas.

What about handling pagination or large result sets?

Check responses for pagination tokens and continue fetching until complete to avoid missing tools or schemas.

rkvst-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/rkvst-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Rkvst Automation via Rube MCP

Automate Rkvst operations through Composio's Rkvst toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/rkvst

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["rkvst"]
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 Rkvst-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `rkvst`
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/rkvst-automation/SKILL.mdView on GitHub

Overview

Automate Rkvst operations using Composio's Rkvst toolkit through Rube MCP. The workflow emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running any task, ensuring you avoid hardcoded tool slugs. It requires a connected Rube MCP and an active Rkvst toolkit connection.

How This Skill Works

First, discover available Rkvst tools with RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Next, check the Rkvst connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, execute the selected tool using RUBE_MULTI_EXECUTE_TOOL with schema-compliant arguments and a memory payload (even if empty).

When to Use It

Automating recurring Rkvst operations (e.g., reconciliations) via MCP.
When tool schemas may change and you must fetch up-to-date slugs.
Before running workflows, verify the Rube MCP connection is ACTIVE.
Executing a sequence of tools in one workflow with a shared session.
Prototyping a new Rkvst task and validating the setup end-to-end.

Quick Start

Step 1: RUBE_SEARCH_TOOLS, queries: [{use_case: "Rkvst operations", known_fields: ""}], session: {generate_id: true}
Step 2: RUBE_MANAGE_CONNECTIONS, toolkits: ["rkvst"], session_id: "<your_session_id>"
Step 3: RUBE_MULTI_EXECUTE_TOOL, tools: [{tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/* schema-compliant args from search results */}}], memory: {}, session_id: "<your_session_id>"

Best Practices

Always call RUBE_SEARCH_TOOLS before any workflow to get current tool schemas.
Verify that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination tokens when present.

Example Use Cases

Nightly Rkvst reconciliation automated by discovering tools, establishing a session, and running the reconciliation tool.
Onboarding a new Rkvst task by fetching up-to-date tool slugs and executing with the required arguments.
Bulk Rkvst operations using RUBE_REMOTE_WORKBENCH and run_composio_tool as part of a scheduled batch.
Debugging a failing Rkvst workflow by re-running RUBE_SEARCH_TOOLS to confirm current schemas and slugs.
Validating the MCP connection status before starting any Rkvst workflow to ensure ACTIVE state.

Frequently Asked Questions

Add this skill to your agents