What is Identitycheck Automation via Rube MCP?

A guided workflow to automate Identitycheck tasks by discovering current tool schemas, ensuring an ACTIVE connection, and executing tools through Rube MCP (Composio) without hardcoding slugs.

Do I always need to search tools before running?

Yes. RUBE_SEARCH_TOOLS fetches the latest tool schemas to ensure you use valid slugs and argument structures.

How can I confirm the connection is ready?

Run RUBE_MANAGE_CONNECTIONS for the identitycheck toolkit and verify that the status is ACTIVE before executing any tools.

identitycheck-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Identitycheck Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/identitycheck

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["identitycheck"]
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 Identitycheck-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `identitycheck`
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/identitycheck-automation/SKILL.md

View on GitHub

Overview

Automate Identitycheck operations using Composio's Identitycheck toolkit through Rube MCP. This skill orchestrates discovery of up-to-date tool schemas, manages authentication and connections, and executes tools in a governed workflow to keep Identitycheck tasks repeatable and adaptable.

How This Skill Works

Technically, you first query RUBE_SEARCH_TOOLS to fetch available Identitycheck tools and their schemas. Next, you verify an active connection with RUBE_MANAGE_CONNECTIONS before running any workflow, and finally execute the selected tool with RUBE_MULTI_EXECUTE_TOOL, ensuring you pass the memory object and the current session_id.

When to Use It

Orchestrating Identitycheck tasks that span multiple tools with current schemas
Setting up or validating Identitycheck connections before running workflows
Working in environments where tool slugs and arguments change frequently
Running a session-scoped Identitycheck workflow with a memory context
Performing bulk Identitycheck operations via remote bench when needed

Quick Start

Step 1: Discover available Identitycheck tools with RUBE_SEARCH_TOOLS (fetch current schemas) and start a session.
Step 2: Establish/verify ACTIVE Identitycheck connection via RUBE_MANAGE_CONNECTIONS using the 'identitycheck' toolkit.
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the tool slug, proper arguments from the search results, include memory: {} and the session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Use exact field names and types from the search results; avoid hardcoding
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty)
Reuse session IDs within a workflow; create new sessions only for new workflows

Example Use Cases

Discover Identitycheck tools and execute a single task end-to-end
Establish and validate an identitycheck connection, then run multiple tools in one session
Dynamically adapt to schema changes by re-fetching tool schemas before execution
Execute several identitycheck tools in sequence using RUBE_MULTI_EXECUTE_TOOL with a shared session
Run bulk Identitycheck operations via RUBE_REMOTE_WORKBENCH using run_composio_tool

Frequently Asked Questions

Add this skill to your agents