Get the FREE Ultimate OpenClaw Setup Guide →

alttext-ai-automation

npx machina-cli add skill ComposioHQ/awesome-claude-skills/alttext-ai-automation --openclaw
Files (1)
SKILL.md
2.9 KB

Alttext AI Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/alttext_ai

Prerequisites

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

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["alttext_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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Alttext AI-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit alttext_ai
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/alttext-ai-automation/SKILL.mdView on GitHub

Overview

Automates Alttext AI operations through Composio's Alttext AI toolkit using Rube MCP. It emphasizes discovering tools first to grab current schemas and ensuring an ACTIVE connection before running workflows for reliable, scalable results.

How This Skill Works

You verify Rube MCP availability with RUBE_SEARCH_TOOLS, then connect to Alttext AI via RUBE_MANAGE_CONNECTIONS, and finally execute discovered tools with RUBE_MULTI_EXECUTE_TOOL using exact schema fields. The tool discovery step returns slugs, input schemas, recommended plans, and pitfalls to guide execution.

When to Use It

  • Batch generate alt text for a large set of product images.
  • Update alt text after a tool schema changes or new tools are released.
  • Ensure an ACTIVE Alttext AI connection before running any workflow.
  • Reuse a session across multiple related Alttext AI tasks within a workflow.
  • Perform bulk or chained tool executions while validating schemas each time.

Quick Start

  1. Step 1: Ensure RUBE MCP is available and use RUBE_SEARCH_TOOLS to discover Alttext AI tools.
  2. Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit alttext_ai and confirm ACTIVE.
  3. Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the correct slug and memory field.

Best Practices

  • Always call RUBE_SEARCH_TOOLS before running a workflow to fetch current schemas.
  • Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to execution.
  • Use exact field names and types from the tool's input schema as returned by discovery.
  • Include memory: {} in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
  • Reuse session IDs where applicable and handle pagination tokens when discovering tools.

Example Use Cases

  • Batch generate alt text for a catalog of 10,000 product images using a single session.
  • Migrate to a new tool slug after a schema change by re-discovering tools first.
  • Audit and refresh alt text across the product catalog after tool updates.
  • Set up a new Alttext AI integration workflow and validate ACTIVE connection before execution.
  • Combine multiple Alttext AI operations in a chained workflow with memory maintained between steps.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers