What is 'RUBE MCP' in this skill?

It's Composio's MCP platform that you connect to and use to search tool schemas.

No, you only need to add the MCP server and authenticate via the toolkit.

What if tool schemas change?

Always run RUBE_SEARCH_TOOLS first to fetch current schemas and avoid hardcoding slugs.

onesignal-user-auth-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/onesignal-user-auth-automation --openclaw

Files (1)

SKILL.md

3.0 KB

Onesignal User Auth Automation via Rube MCP

Automate Onesignal User Auth operations through Composio's Onesignal User Auth toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/onesignal_user_auth

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["onesignal_user_auth"]
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 Onesignal User Auth-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `onesignal_user_auth`
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/onesignal-user-auth-automation/SKILL.md

View on GitHub

Overview

Automate tasks for Onesignal User Auth using Composio's toolkit and the Rube MCP platform. It centralizes tool discovery, connection validation, and tool execution, ensuring auth workflows stay in sync with the latest tool schemas.

How This Skill Works

First discover available tools with RUBE_SEARCH_TOOLS to fetch current slugs and input schemas. Then verify your Onesignal auth connection with RUBE_MANAGE_CONNECTIONS and execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, passing exact arguments and a session_id. Always include memory as required; reuse sessions for related tasks and re-run searches when schemas change.

When to Use It

Automating recurring Onesignal User Auth tasks via Rube MCP
Ensuring current tool schemas before running auth workflows
Verifying ACTIVE Onesignal auth connections prior to execution
Executing multiple auth tasks in a single workflow with RUBE_MULTI_EXECUTE_TOOL
Reusing a session ID across a sequence of related auth operations

Quick Start

Step 1: Add Rube MCP endpoint https://rube.app/mcp to your client and verify RUBE_SEARCH_TOOLS.
Step 2: Run RUBE_SEARCH_TOOLS for Onesignal User Auth use case and note the tool_slug.
Step 3: Run RUBE_MANAGE_CONNECTIONS to activate toolkit, then execute the tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and schemas
Check RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools
Use exact field names and types from the search results; avoid hardcoding slugs
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow; generate a new one for separate flows

Example Use Cases

Discover tools for Onesignal User Auth, connect, and run a token refresh tool with a valid session
Bulk update several user records by discovering the appropriate tool slugs and executing them in one session
Set up a new Onesignal User Auth connection and run a health-check workflow
Iterate through a sequence of auth operations by reusing the same session ID
Handle tool schema updates by re-running RUBE_SEARCH_TOOLS before automation

Frequently Asked Questions

Add this skill to your agents