What is required to set up?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available and an active Auth0 connection using the toolkit 'auth0'.

Why should I search tools first?

Tool schemas change over time; searching ensures you use current slugs and argument names rather than hardcoding.

How do I run a workflow?

Discover tools with RUBE_SEARCH_TOOLS, verify the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then execute with RUBE_MULTI_EXECUTE_TOOL including memory and a session_id.

auth0-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Auth0 Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/auth0

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Auth0 operations through Composio's toolkit using Rube MCP. This skill guides you to discover current tool schemas, manage connections, and execute workflows without hardcoding tool slugs. Always start with RUBE_SEARCH_TOOLS to stay in sync with schema changes.

How This Skill Works

The workflow begins with RUBE_SEARCH_TOOLS to fetch available Auth0 task tools and their input schemas. Next, you verify and activate your Auth0 connection using RUBE_MANAGE_CONNECTIONS. Finally, you execute the chosen, discovered tool with RUBE_MULTI_EXECUTE_TOOL, providing the tool slug, schema-compliant arguments, a memory payload, and a session_id.

When to Use It

Starting a new Auth0 automation task and needing the latest tool schemas
Setting up or validating an Auth0 connection before running workflows
Selecting and executing a specific Auth0 operation using the discovered tool arguments
Maintaining state across a multi-step workflow by reusing session IDs and memory
Performing bulk Auth0 tasks while staying aligned with current schemas (no hardcoding)

Quick Start

Step 1: Verify Rube MCP is available and RUBE_SEARCH_TOOLS responds for Auth0
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'auth0' and ensure the connection status is ACTIVE
Step 3: Use RUBE_MULTI_EXECUTE_TOOL with a discovered TOOL_SLUG, proper arguments, memory, and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results
Include memory: {} in every RUBE_MULTI_EXECUTE_TOOL call
Reuse session IDs within a workflow and manage pagination if necessary

Example Use Cases

Discover Auth0 operations and execute a user-creation workflow using a discovered tool slug
Connect to Auth0 and verify the connection is ACTIVE before running any tasks
Update user metadata in Auth0 by selecting the appropriate tool from the discovered set
List available Auth0 operations and run a targeted task with proper input schemas
Bulk update roles or permissions for multiple users using a discovered tool within a single session

Frequently Asked Questions

Add this skill to your agents