PromptShop

Rkvst Automation

It's designed for users who want to streamline data management and governance tasks within Rkvst.

Install

npx promptshop add rkvst-automation

Details

What This Skill Does

This skill automates Rkvst operations using Composio's Rkvst toolkit through Rube MCP. It's designed for users who want to streamline data management and governance tasks within Rkvst. The skill requires an active Rkvst connection and utilizes Rube MCP for tool discovery and execution.

When to Use

  • Manage data assets in Rkvst.
  • Track data lineage.
  • Enforce data governance policies.
  • Automate data compliance tasks.
  • Generate data audit reports.
  • Secure data access.

Key Features

  • Automates Rkvst tasks via Rube MCP.
  • Uses Composio's Rkvst toolkit.
  • Discovers available tools using RUBE_SEARCH_TOOLS.
  • Manages connections with RUBE_MANAGE_CONNECTIONS.
  • Executes tools with RUBE_MULTI_EXECUTE_TOOL.
  • Provides setup instructions and known pitfalls.

Manual Installation

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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Rkvst-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit rkvst
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Automate Rkvst operations through Composio's Rkvst toolkit via Rube MCP. Toolkit docs: composio.dev/toolkits/rkvst