$ ~/registry/skill/composiohq-composio-skills-alttext-ai-automation

SKILL

alttext-ai-automation

Name: alttext-ai-automation
Author: Composio

Automate Alttext AI workflows through Rube MCP for image alt text tasks.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be an open-source prompt/template with strong community trust and no clear malicious indicators. The main caution is that it directs users to connect Rube MCP and authorize an Alttext AI integration, so network egress, account scope, and downstream tool capabilities should be reviewed separately.

CredentialsCaution

The material says the skill itself requires no API keys, but the README requires an active `alttext_ai` connection via `RUBE_MANAGE_CONNECTIONS` and asks the user to complete an auth link, implying OAuth or session-based authorization. There is no explicit instruction to paste raw secrets, so the main credential risk comes from third-party connection authorization rather than the skill source itself.

Network egressCaution

The README explicitly instructs users to add `https://rube.app/mcp` as an MCP server and use Composio/Rube to invoke Alttext AI tools, so user requests, session identifiers, and task arguments are expected to be sent to external services. The endpoint and purpose are documented, but the exact transmitted fields and downstream forwarding scope are not fully disclosed in the provided material.

Code executionCaution

This item is marked as `prompt-only`, and there is no local installer, binary, or direct system command execution described, so the skill itself does not present inherent local code execution risk. However, it orchestrates external tool calls such as `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`; the effective execution power depends on the connected MCP/toolkit and should be reviewed separately.

Data accessCaution

The material does not state that the skill directly reads or writes local files; data access is more likely to occur within the authorized Alttext AI/Composio session. Because the README encourages session reuse, pagination, and bulk operations, the effective data scope depends on the connected account permissions and specific tool schemas. The material does not show excessive local data access, but it also does not define strict least-privilege boundaries on the service side.

Supply chainLow risk

The source is an open GitHub repository, and the system flags it as `open-source` with high community adoption (64.7k stars), which are strong risk-reducing signals. Although the license is undeclared and maintenance status is unknown, and it depends on external Rube/Composio services, the skill text itself is reasonably auditable and comes from a generally credible source with no clear supply-chain red flags.

Recommendations

Before connecting to `https://rube.app/mcp`, review the privacy, retention, and forwarding policies of Rube/Composio and Alttext AI.
Grant only the minimum account permissions needed for the `alttext_ai` connection, and regularly revoke unused authorized sessions.
Inspect the actual schemas returned by `RUBE_SEARCH_TOOLS` before execution to ensure no unnecessary images, text, or metadata are uploaded.
If used in an enterprise environment, monitor the MCP and downstream SaaS traffic through egress logging or a controlled proxy.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "alttext-ai-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/alttext-ai-automation/SKILL.md
2. Save it as ~/.claude/skills/alttext-ai-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit alttext_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: "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

Automate Autom workflows via Rube MCP while checking current tool schemas first.

ComposioGet→

$ loading_