Astica AI Automation

What This Skill Does

This skill automates interactions with the Astica AI platform through Composio's Rube MCP. It enables users to programmatically access and utilize Astica AI's image and video analysis capabilities. This is ideal for developers and researchers looking to integrate AI-powered media analysis into their projects.

When to Use

• Analyze images for object detection.
• Identify faces and facial attributes.
• Extract text from images using OCR.
• Detect inappropriate content in videos.
• Automate image tagging and categorization.
• Integrate AI analysis into media workflows.

Key Features

• Automates Astica AI operations.
• Uses Rube MCP for tool management.
• Discovers available tools via RUBE_SEARCH_TOOLS.
• Checks connection status before execution.
• Enforces schema compliance for arguments.
• Provides a structured workflow pattern.

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

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

Quick Reference