About this skill

Problem Solved

When Astica AI tool schemas change, connection state must be verified, and multi-tool execution requires stable sessions and pagination, hard-coding calls becomes fragile. This skill turns those Astica AI automation tasks into a repeatable engineering flow: discover the available tools first, then execute the workflow.

How It Works

It relies on Rube MCP and Composio's astica_ai toolkit, with an explicit preference for dynamic discovery over fixed invocations. The main steps are:

Use RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, recommended execution plans, and known pitfalls
Use RUBE_MANAGE_CONNECTIONS to confirm the astica_ai connection is ACTIVE
Use RUBE_MULTI_EXECUTE_TOOL to run discovered tools while keeping the memory parameter present
Use RUBE_REMOTE_WORKBENCH for bulk operations and RUBE_GET_TOOL_SCHEMAS when a full schema is needed

Boundaries and Caveats

The skill assumes Rube MCP is already connected and Astica AI authorization is valid; it does not create underlying accounts. Tool schemas may change, so tool names, argument structures, and pagination behavior should not be hard-coded. Reuse the session within a workflow, generate a new session for a new workflow, and keep fetching pagination tokens until the response is complete.

Screenshots

Use Cases

After connecting Rube MCP in an agent client, discover available Astica AI tools and schemas before invoking them.
When the Astica AI connection is inactive, complete the auth link flow and confirm the status is ACTIVE.
During multi-tool workflows, reuse the session and follow pagination tokens until the response is complete.
When full parameter definitions are needed, fetch the schemaRef tool schema via RUBE_GET_TOOL_SCHEMAS.

Best For

AI engineers integrating Composio tools who need stable discovery and execution of Astica AI tools.
MCP workflow engineers who need to verify Rube MCP and Astica AI connection state before invocation.
Automation script developers who need to handle changing tool schemas, memory parameters, and pagination.
Product engineers integrating external SaaS services who need to route Astica AI operations into a unified agent flow.