home / skills / composiohq / awesome-claude-skills / axonaut-automation

axonaut-automation skill

safe

/axonaut-automation

This skill automates Axonaut operations via Rube MCP, discovering current tool schemas first to ensure accurate, up-to-date automation workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill axonaut-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: axonaut-automation
description: "Automate Axonaut tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Axonaut Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/axonaut](https://composio.dev/toolkits/axonaut)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Axonaut connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `axonaut`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `axonaut`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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_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 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](https://composio.dev)*

Overview

This skill automates Axonaut tasks by orchestrating Composio’s Axonaut toolkit through a Rube MCP connection. It guides tool discovery, connection checks, and schema-compliant execution so workflows run reliably. It emphasizes searching tools first and reusing session context for consistent automation.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to discover current tool slugs, input schemas, and recommended execution plans. It validates an Axonaut connection via RUBE_MANAGE_CONNECTIONS and then runs operations with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH. Calls always include memory and session IDs and follow the exact field names and types returned by the search step.

When to use it

Automate CRM tasks in Axonaut like contacts, invoices, or opportunities
Build repeatable workflows that must adapt to changing tool schemas
Run bulk operations through Composio tool chains
Integrate Axonaut operations into broader agent workflows or pipelines
Execute schema-sensitive calls where exact input shapes are required

Best practices

Always call RUBE_SEARCH_TOOLS first to fetch live tool slugs and input schemas
Verify toolkit connection via RUBE_MANAGE_CONNECTIONS and ensure status is ACTIVE
Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session_id within a workflow; generate new session_ids for new workflows
Respect pagination tokens and fetch until responses are complete

Example use cases

Create or update Axonaut contacts by discovering the contact tool schema and passing schema-compliant fields
Generate invoices in bulk using RUBE_REMOTE_WORKBENCH and run_composio_tool() for batch processing
Link opportunities to contacts after confirming active Axonaut connection and using discovered tool inputs
Build an agent workflow that reads data from another system, discovers the right Axonaut tool, then executes the create or update call

FAQ

What must I do before executing any Axonaut tool?

Always run RUBE_SEARCH_TOOLS to get the current tool schema and then confirm the Axonaut connection is ACTIVE with RUBE_MANAGE_CONNECTIONS.

Can I hardcode tool slugs and inputs?

No. Tool slugs and input schemas change. Hardcoding risks failures; always fetch live schemas before execution.