signaturely-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/signaturely-automation --openclawSignaturely Automation via Rube MCP
Automate Signaturely operations through Composio's Signaturely toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/signaturely
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Signaturely connection via
RUBE_MANAGE_CONNECTIONSwith toolkitsignaturely - 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 toolkitsignaturely - 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: "Signaturely 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 Signaturely task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["signaturely"]
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 Signaturely-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit signaturely |
| 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/signaturely-automation/SKILL.mdView on GitHub Overview
Signaturely Automation via Rube MCP lets you orchestrate Signaturely actions through Composio's toolkit. It emphasizes always discovering current tool schemas with RUBE_SEARCH_TOOLS before running a workflow and requires an ACTIVE Signaturely connection via RUBE_MANAGE_CONNECTIONS. This makes automation resilient to schema changes and credential setups.
How This Skill Works
It discovers available Signaturely tools for your task using RUBE_SEARCH_TOOLS, then checks the connection with RUBE_MANAGE_CONNECTIONS. Finally, it executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory (even if empty) and a session_id to maintain continuity.
When to Use It
- Automating recurring Signaturely signing workflows to save time and reduce manual steps.
- Dynamically discovering current Signaturely tool schemas before building or updating workflows.
- Verifying and maintaining an ACTIVE Signaturely connection via RUBE_MANAGE_CONNECTIONS prior to execution.
- Executing a discovered tool with precise, schema-compliant arguments and a memory payload.
- Handling tool schema changes and pagination to avoid hardcoding tool slugs or parameters.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'signaturely' and ensure the status is ACTIVE.
- Step 3: Use RUBE_SEARCH_TOOLS to discover tools for your use case, then execute with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and a memory payload.
Best Practices
- Always call RUBE_SEARCH_TOOLS before running workflows to fetch current tool schemas.
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
- Use exact field names and types from the security-search results; avoid hardcoding slugs.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and generate new ones for new executions; watch for pagination tokens.
Example Use Cases
- A weekly contract signing pipeline that discovers the appropriate Signaturely tool, connects to the toolkit, and signs multiple documents automatically.
- A diagnostics flow that lists available Signaturely tools and their input schemas to adapt an automation without code changes.
- A single-document signing flow that uses a tool slug from search results and runs with runtime-provided arguments.
- A long-running batch process that reuses a session ID across multiple Signaturely tasks within one workflow.
- A bulk operation using RUBE_REMOTE_WORKBENCH to run several Signaturely tool executions in one go.
