tisane-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/tisane-automation --openclawTisane Automation via Rube MCP
Automate Tisane operations through Composio's Tisane toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/tisane
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Tisane connection via
RUBE_MANAGE_CONNECTIONSwith toolkittisane - 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 toolkittisane - 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: "Tisane 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 Tisane task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["tisane"]
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 Tisane-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit tisane |
| 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/tisane-automation/SKILL.mdView on GitHub Overview
tisane-automation automates Tisane operations through Composio's Rube MCP toolkit. It relies on RUBE_SEARCH_TOOLS to fetch current tool schemas and requires an active tisane connection via RUBE_MANAGE_CONNECTIONS. Always search for tools first to adapt to evolving schemas.
How This Skill Works
Technically, you first discover available tools with RUBE_SEARCH_TOOLS, then verify an ACTIVE tisane connection with RUBE_MANAGE_CONNECTIONS, and finally execute one or more tools using RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and properly formatted arguments, including memory and a session_id.
When to Use It
- Automating daily or recurring Tisane workflows where tool schemas change over time.
- Orchestrating a sequence of tisane operations in a single session without hardcoding tool slugs.
- Validating that the tisane connection is ACTIVE before running any workflows.
- Batching multiple tisane tool executions in a single session for efficiency.
- Handling schema updates by re-discovering tools instead of manual edits.
Quick Start
- Step 1: Run RUBE_SEARCH_TOOLS to fetch current Tisane tool schemas.
- Step 2: Ensure the tisane toolkit is ACTIVE using RUBE_MANAGE_CONNECTIONS.
- Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper arguments, memory, and a session_id.
Best Practices
- Always run RUBE_SEARCH_TOOLS first to fetch current tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Pass exact field names and types from the search results; avoid hardcoding.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({ }).
- Reuse session IDs within a workflow and generate new ones for new workflows.
Example Use Cases
- Daily Tisane reconciliation automated end-to-end using discovered tool slugs and a reused session.
- Automated tisane status checks by discovering tools first, then executing a status tool with the ACTIVE connection.
- Bulk tisane operations: discover tooling, verify, then run multiple tools in a single session via RUBE_MULTI_EXECUTE_TOOL.
- Adapt to schema changes by re-discovering tools instead of hardcoding slugs, ensuring robust automation.
- Create a reusable tisane workflow template that enforces memory payloads in every execute call.
