eversign-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/eversign-automation --openclawEversign Automation via Rube MCP
Automate Eversign operations through Composio's Eversign toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/eversign
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Eversign connection via
RUBE_MANAGE_CONNECTIONSwith toolkiteversign - 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 toolkiteversign - 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: "Eversign 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 Eversign task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["eversign"]
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 Eversign-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit eversign |
| 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/eversign-automation/SKILL.mdView on GitHub Overview
Automate Eversign operations through Composio's Eversign toolkit by using the Rube MCP. This skill enforces discovering tool schemas with RUBE_SEARCH_TOOLS first and only proceeds when the Eversign connection is ACTIVE. It enables end-to-end automation from tool discovery to execution with safe session and memory handling.
How This Skill Works
The workflow starts by querying available Eversign tools with RUBE_SEARCH_TOOLS, then validates the toolkit connection via RUBE_MANAGE_CONNECTIONS. When ready, it executes the chosen tool using RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, proper arguments from the schema, a memory payload, and a session_id to maintain context.
When to Use It
- When you need to automate a specific Eversign operation without hardcoding tool slugs, ensuring you always fetch current schemas first.
- When you must verify the Rube MCP connection is ACTIVE before running any Eversign workflows.
- When orchestrating multiple Eversign actions in a single workflow and requiring a persistent session.
- When changes to tool schemas occur and you want to avoid broken automations by re-reading schemas.
- When performing bulk or repeated Eversign tasks by using the remote bench or multi-tool execution flow.
Quick Start
- Step 1: Get Rube MCP by adding https://rube.app/mcp as an MCP server in your client configuration.
- Step 2: Verify availability with RUBE_SEARCH_TOOLS and fetch current Eversign tool schemas.
- Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkit: ["eversign"], then run a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and proper arguments.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing to get updated tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running any tools.
- Use exact field names and types from the search results; do not hardcode slugs or arguments.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty (memory: {}).
- Reuse session IDs within a workflow and generate new ones for new runs.
Example Use Cases
- Discover an Eversign operation slug with RUBE_SEARCH_TOOLS and execute it with RUBE_MULTI_EXECUTE_TOOL using the returned schema.
- If the Eversign connection becomes inactive, re-authenticate via RUBE_MANAGE_CONNECTIONS and retry.
- Chain several Eversign tasks in one run by reusing a session_id and memory across multiple RUBE_MULTI_EXECUTE_TOOL calls.
- Review full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs before integration.
- Perform bulk Eversign actions using RUBE_REMOTE_WORKBENCH to run multiple composio tools in parallel.
