userlist-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/userlist-automation --openclawUserlist Automation via Rube MCP
Automate Userlist operations through Composio's Userlist toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/userlist
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Userlist connection via
RUBE_MANAGE_CONNECTIONSwith toolkituserlist - 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 toolkituserlist - 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: "Userlist 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 Userlist task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["userlist"]
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 Userlist-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit userlist |
| 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/userlist-automation/SKILL.mdView on GitHub Overview
This skill automates Userlist operations by leveraging Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before executing any workflow and requires an ACTIVE Userlist connection for reliable automation.
How This Skill Works
Begin by adding the MCP server and verifying RUBE_SEARCH_TOOLS to obtain current tool slugs and input schemas. Next, confirm an ACTIVE Userlist connection with RUBE_MANAGE_CONNECTIONS, and finally execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments, always including memory: {}.
When to Use It
- When you need to automate repetitive Userlist tasks without manual tool lookup.
- When tool schemas may change and you must fetch current slugs before execution.
- When integrating Userlist workflows into scheduling or CI pipelines.
- When performing multiple Userlist operations in one session and reusing session IDs.
- When handling large user lists with pagination and incremental fetch.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds.
- Step 2: Run RUBE_MANAGE_CONNECTIONS with toolkit ["userlist"] and ensure the status is ACTIVE.
- Step 3: Use RUBE_SEARCH_TOOLS to discover a tool, then execute it with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory: {}.
Best Practices
- Always call RUBE_SEARCH_TOOLS before selecting a tool slug.
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution.
- Use the 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 for related tasks and handle pagination tokens until complete.
Example Use Cases
- Onboarding: discover an add_user tool and run it with a new user payload to add a user to Userlist.
- Bulk status update: discover a bulk_update tool and apply a list of changes in a single run.
- Scheduled sync: fetch tool schemas, verify the connection, and run a tool to sync external user data into Userlist on a timer.
- Multi-tool run: in a single workflow, discover tools, connect, and execute multiple tools by reusing the session_id.
- Pagination-aware fetch: list users with a tool that returns pagination tokens and continue requesting until complete.
