What is required to start using astica-ai-automation?

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) and an active Astica AI connection via RUBE_MANAGE_CONNECTIONS with toolkit astica_ai. Always call RUBE_SEARCH_TOOLS first to get current tool schemas.

How do I discover available Astica AI tools?

Use RUBE_SEARCH_TOOLS with a use_case like 'Astica AI operations' to retrieve tool slugs, input schemas, recommended execution plans, and known pitfalls.

How do I execute a tool once discovered?

Call RUBE_MULTI_EXECUTE_TOOL with the tool_slug from the search results, provide the exact schema-compliant arguments, and include memory (even if empty) and a session_id.

astica-ai-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/astica-ai-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Astica AI Automation via Rube MCP

Automate Astica AI operations through Composio's Astica AI toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/astica_ai

Prerequisites

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

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit astica_ai
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: "Astica AI 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 Astica AI task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["astica_ai"]
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 Astica AI-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `astica_ai`
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/astica-ai-automation/SKILL.mdView on GitHub

Overview

Automate Astica AI operations through Composio's Astica AI toolkit using Rube MCP. Always fetch current tool schemas with RUBE_SEARCH_TOOLS and ensure an active Astica AI connection before running workflows.

How This Skill Works

Discover available Astica AI tools with RUBE_SEARCH_TOOLS, then verify an ACTIVE connection via RUBE_MANAGE_CONNECTIONS for the astica_ai toolkit. Finally, execute one or more tools using RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and proper arguments, always including memory and a session_id.

When to Use It

You need to automate routine Astica AI tasks and want up-to-date tool schemas before execution.
You are updating or validating tool schemas after changes and need to avoid hardcoding slugs.
You are setting up a new Astica AI workflow and must ensure a live, ACTIVE connection first.
You plan to run multiple Astica AI tools in a single workflow (bulk operations).
You want to maintain state across steps by reusing a session_id within a workflow.

Quick Start

Step 1: 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.
Step 2: Verify connectivity: Run RUBE_SEARCH_TOOLS to confirm the server responds and tool schemas are available.
Step 3: Connect and execute: Run RUBE_MANAGE_CONNECTIONS with toolkit astica_ai, ensure ACTIVE, then use RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug and proper arguments, including memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to pull current tool schemas.
Check that the connection status from RUBE_MANAGE_CONNECTIONS is ACTIVE before executing tools.
Use exact field names and types as returned by the tool search results.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if it is an empty object.
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Daily Astica AI data prep and inference pipeline that discovers tools and runs them in sequence.
Multi-tool orchestration where a preprocessing tool is followed by an inference tool.
Automated validation of tool schemas after a schema update.
Bulk execution of several Astica AI tasks via RUBE_MULTI_EXECUTE_TOOL.
Session-scoped workflow for streaming inputs with a shared session_id.

Frequently Asked Questions

Add this skill to your agents