"Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas."
Install
npx skillscat add composiohq/awesome-claude-skills/21risk-automation Install via the SkillsCat registry.
This skill enables automated interaction with 21risk's API through Composio's Rube MCP integration, allowing agents to perform 21risk tasks programmatically. It addresses the need to dynamically discover current tool schemas and manage authentication connections before executing workflows. Developers should use it when building agents that need to automate 21risk operations, ensuring they search for available tools first to handle schema changes.
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_CONNECTIONSwith toolkit_21risk - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkit_21risk - 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: "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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 21risk-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit _21risk |
| 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