alttext-ai-automation
Automate Alttext AI tasks via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:ComposioHQ/awesome-claude-skills --skill alttext-ai-automation75
Quality
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./composio-skills/alttext-ai-automation/SKILL.mdDiscovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid template for Alttext AI automation via Rube MCP with clear workflow sequencing and good structural organization. The main weaknesses are moderate redundancy in emphasizing 'always search first' and the inherently abstract nature of the tool calls (since actual schemas must be discovered at runtime). The Known Pitfalls section adds practical value.
Suggestions
Remove redundant 'always search first' messaging - state it once prominently in Prerequisites or a callout box
Consider adding a concrete example showing a complete workflow with actual Alttext AI use case (e.g., generating alt text for an image) with realistic response handling
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is reasonably efficient but includes some redundancy (e.g., 'Always search first' appears multiple times, and the workflow pattern repeats concepts from earlier sections). The quick reference table adds value but some explanatory text could be tightened. | 2 / 3 |
Actionability | Provides concrete tool call patterns with parameter examples, but these are pseudocode-style representations rather than executable code. The actual tool schemas and arguments are deferred to runtime discovery, which is intentional but reduces immediate actionability. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint (verify ACTIVE status before executing) and the Known Pitfalls section provides error recovery guidance. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to Composio docs is one level deep and clearly signaled. Quick reference table provides scannable summary. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.