home / skills / composiohq / awesome-claude-skills / alttext-ai-automation

alttext-ai-automation skill

/alttext-ai-automation

This skill automates Alttext AI operations via Rube MCP, always discovering current tool schemas before execution to ensure up-to-date workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill alttext-ai-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: alttext-ai-automation
description: "Automate Alttext AI tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# 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](https://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

| Operation | Approach |
|-----------|----------|
| Find tools | `RUBE_SEARCH_TOOLS` with Alttext AI-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `alttext_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](https://composio.dev)*

Overview

This skill automates Alttext AI tasks through Composio's Alttext AI toolkit using the Rube MCP orchestration layer. It provides a repeatable workflow: discover tools, verify connections, and execute toolkit operations reliably. The skill emphasizes always searching for current tool schemas before any execution to avoid breaking changes.

How this skill works

On each run the skill first calls RUBE_SEARCH_TOOLS to retrieve available tool slugs, input schemas, and execution recommendations. It then verifies an active Alttext AI connection via RUBE_MANAGE_CONNECTIONS and uses RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs) to run schema-compliant operations. The skill insists on including a memory object, reusing session IDs within a workflow, and handling pagination on responses.

When to use it

  • Automating image alt-text generation or updates at scale
  • Integrating Alttext AI into a content publishing pipeline
  • Running batch operations or bulk transformations via Composio toolkits
  • Orchestrating multi-step Alttext AI workflows where tool schemas may change
  • Building developer tools that must discover and adapt to live toolkit schemas

Best practices

  • Always call RUBE_SEARCH_TOOLS first — tool slugs and field schemas can change
  • Confirm toolkit connection status with RUBE_MANAGE_CONNECTIONS and follow any provided auth links until status is ACTIVE
  • Use exact field names and types returned by search results; never hardcode argument shapes
  • Include a memory parameter (even an empty {}) in RUBE_MULTI_EXECUTE_TOOL calls
  • Reuse session IDs for related operations; generate new session IDs for separate workflows
  • Check responses for pagination tokens and loop until full results are retrieved

Example use cases

  • Discover current Alttext AI tools, then run a single-image alt-text generation using RUBE_MULTI_EXECUTE_TOOL
  • Authenticate or reauthorize the alttext_ai toolkit via RUBE_MANAGE_CONNECTIONS before scheduled batch runs
  • Perform a bulk alt-text audit and update using RUBE_REMOTE_WORKBENCH with run_composio_tool() for parallel processing
  • Build a CI step that fetches RUBE_GET_TOOL_SCHEMAS to validate expected input shapes before deployment
  • Orchestrate a multi-step pipeline: discover tools, enrich metadata, generate alt-text, and store outputs in a content database

FAQ

What is the first call I should make when using this skill?

Always call RUBE_SEARCH_TOOLS to discover available tools and their exact schemas before doing anything else.

What if the connection is not ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup, then confirm the connection shows ACTIVE before executing tools.