What are the prerequisites?

RUBE_SEARCH_TOOLS must be available; Endorsal must be connected via RUBE_MANAGE_CONNECTIONS with the toolkit endorsal; and you should call RUBE_SEARCH_TOOLS first to obtain current tool schemas.

Do I need to hardcode tool slugs?

No. Always search for tool schemas with RUBE_SEARCH_TOOLS before executing and use the slugs from the results.

How do I ensure successful execution?

Confirm the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, include memory in RUBE_MULTI_EXECUTE_TOOL calls, and use the exact field names/types from the search results while reusing or generating a session_id for the workflow.

endorsal-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Endorsal Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/endorsal

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Endorsal operations through Composio's Endorsal toolkit using Rube MCP. The skill emphasizes discovering current tool schemas before execution to avoid hardcoding slugs or arguments, then connects to Endorsal and runs tools with structured memory and session handling.

How This Skill Works

The workflow begins by querying RUBE_SEARCH_TOOLS to fetch Endorsal tool slugs and input schemas. It then validates the Endorsal connection with RUBE_MANAGE_CONNECTIONS and proceeds to execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, the required arguments from the schema, memory, and a session_id. This approach keeps tool definitions up to date and ensures safe, schema-compliant executions.

When to Use It

When starting a new Endorsal automation and you need up-to-date tool schemas
When you need to verify the Endorsal connection is ACTIVE before executing tools
When executing a discovered tool using the exact field names and types from the search results
When maintaining state across tasks by reusing a session_id within a workflow
When handling tool changes or large workflows by re-running RUBE_SEARCH_TOOLS before execution

Quick Start

Step 1: Ensure Rube MCP is connected and RUBE_SEARCH_TOOLS responds
Step 2: Discover Endorsal tools with RUBE_SEARCH_TOOLS for use_case "Endorsal operations" and capture slugs and schemas
Step 3: Execute a tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug, proper arguments, memory, and a session_id

Best Practices

Always search for tool schemas first to avoid hardcoding slugs or arguments
Check that the Endorsal connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before execution
Use exact field names and types from the RUBE_SEARCH_TOOLS results
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow or generate new IDs for new tasks

Example Use Cases

Automate a monthly Endorsal endorsements batch by discovering all tools, then executing with proper arguments and memory
Reconnect Endorsal when RUBE_MANAGE_CONNECTIONS reports INACTIVE using the provided auth flow
Submit an endorsement for a user by discovering the specific tool slug via RUBE_SEARCH_TOOLS and executing with required fields
Perform bulk Endorsal tasks through RUBE_REMOTE_WORKBENCH using run_composio_tool for efficiency
Run a multi-step Endorsal workflow that reuses a session_id across steps to endorse multiple users in sequence

Frequently Asked Questions

Add this skill to your agents