Get the FREE Ultimate OpenClaw Setup Guide →
npx machina-cli add skill ranbot-ai/awesome-skills/21risk-automation --openclaw
Files (1)
SKILL.md
3.0 KB

21risk Automation via Rube MCP

Automate 21risk operations through Composio's 21risk toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/_21risk

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["_21risk"]
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 21risk-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit _21risk
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

Powered by Composio

Source

git clone https://github.com/ranbot-ai/awesome-skills/blob/main/skills/21risk-automation/SKILL.mdView on GitHub

Overview

Automate 21risk operations using Composio's Rube MCP toolkit. This skill emphasizes discovering current tool schemas first (RUBE_SEARCH_TOOLS) and verifying an active connection (RUBE_MANAGE_CONNECTIONS) before running workflows, ensuring resilient automation of risk tasks.

How This Skill Works

Begin by discovering available 21risk tools with RUBE_SEARCH_TOOLS to obtain up-to-date input schemas. Then verify the connection via RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally, execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, correct arguments, a memory payload, and the current session_id.

When to Use It

  • Automating daily or batch 21risk operations across multiple tasks
  • When tool schemas change and you must fetch latest definitions before running
  • When you need to reuse a session across a workflow to maintain context
  • When ensuring RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
  • When performing bulk or chained 21risk tasks in a single run

Quick Start

  1. Step 1: Verify RUBE_SEARCH_TOOLS responds and returns current 21risk tool schemas
  2. Step 2: Manage connection with RUBE_MANAGE_CONNECTIONS for toolkit _21risk and ensure ACTIVE
  3. Step 3: Discover a tool slug from the search results and run it with RUBE_MULTI_EXECUTE_TOOL using memory and the current session_id

Best Practices

  • Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
  • Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  • Use exact field names and types from the search results
  • Always include memory in RUBE_MULTI_EXECUTE_TOOL calls
  • Reuse session IDs within a workflow; generate new ones for new workflows

Example Use Cases

  • Schedule a daily 21risk risk-entry creation and status updates by discovering tools each morning and executing them in a single session
  • Fetch latest 21risk schemas and run a risk assessment, then export results to a dashboard
  • Bulk update 21risk tasks for a batch of risk records using RUBE_MULTI_EXECUTE_TOOL with memory
  • Chain discovery, connection check, and tool execution in one persistent session for a multi-step workflow
  • Execute a sequence of 21risk operations via RUBE_REMOTE_WORKBENCH's run_composio_tool for bulk processing

Frequently Asked Questions

Add this skill to your agents

Related Skills

Sponsor this space

Reach thousands of developers