axonaut-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/axonaut-automation --openclawAxonaut Automation via Rube MCP
Automate Axonaut operations through Composio's Axonaut toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/axonaut
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Axonaut connection via
RUBE_MANAGE_CONNECTIONSwith toolkitaxonaut - 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 toolkitaxonaut - 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: "Axonaut 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 Axonaut task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["axonaut"]
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 Axonaut-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit axonaut |
| 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/axonaut-automation/SKILL.mdView on GitHub Overview
Automate Axonaut operations through Composio's Axonaut toolkit using Rube MCP. It emphasizes discovering current tool schemas first, establishing a connection, and executing tools in a structured workflow so Axonaut tasks run reliably and scalably.
How This Skill Works
The workflow starts by discovering available Axonaut tools with RUBE_SEARCH_TOOLS, then checks or establishes a connection with RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool using RUBE_MULTI_EXECUTE_TOOL. Always include the memory parameter and reuse session IDs where appropriate to maintain context across steps.
When to Use It
- Automating Axonaut tasks like invoices or customer updates and adapting to current tool schemas.
- Dynamically selecting the right tool after discovering available Axonaut tools.
- Ensuring the Axonaut connection is ACTIVE before running any workflows.
- Orchestrating multiple Axonaut tools within a single session.
- Handling tool schema changes and pagination without hardcoding tool slugs.
Quick Start
- Step 1: Ensure Rube MCP is configured and RUBE_SEARCH_TOOLS responds.
- Step 2: Discover available Axonaut tools with RUBE_SEARCH_TOOLS for Axonaut operations.
- Step 3: Connect to Axonaut with RUBE_MANAGE_CONNECTIONS and execute a discovered tool using RUBE_MULTI_EXECUTE_TOOL, including memory and the appropriate session.
Best Practices
- Always call RUBE_SEARCH_TOOLS before any workflow to get current tool schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before tool execution.
- Use exact field names and types from the search results; avoid hardcoding slugs or arguments.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow and generate new ones for separate tasks; handle pagination if present.
Example Use Cases
- Auto-create an Axonaut invoice when an e-commerce order is placed and linked to Axonaut.
- Sync new customer signups from a CRM into Axonaut as contacts or customers.
- Bulk update contact details in Axonaut from a spreadsheet or external system.
- Generate a monthly financial overview by chaining Axonaut tools and consolidating results.
- Audit and adapt tool usage when tool schemas change to avoid broken automations.
