CtrlK
BlogDocsLog inGet started
Tessl Logo

amara-automation

Automate Amara tasks via Rube MCP (Composio). Always search tools first for current schemas.

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/amara-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, concise, and provides concrete tool-call templates for a dynamically-specified integration, with the main weakness being a missing post-execution validation feedback loop for batch operations.

Suggestions

Add an explicit post-execution validation step in the Core Workflow (e.g., check results, handle pagination tokens, retry on failure) to establish a feedback loop for batch operations.

Reduce redundancy between the Prerequisites, Step 1, and 'Always search first' pitfall so discovery guidance appears once and authoritatively.

Provide one fully fleshed-out example with real-looking argument values to lift actionability from mostly-executable to copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean with short sections and code blocks that assume Claude's competence, with only minor redundancy (discovery is restated in Step 1 and the 'Always search first' pitfall echoes the prerequisites), fitting the efficient-with-minor-trim anchor.

4 / 5

Actionability

Concrete RUBE_* tool calls with parameter shapes are provided, but arguments use placeholders ('your specific Amara task', 'TOOL_SLUG_FROM_SEARCH', schema-compliant args comment) rather than copy-paste-ready values, placing it at mostly-executable with minor gaps.

4 / 5

Workflow Clarity

The setup-to-execution sequence is clear with ACTIVE-status checkpoints, but RUBE_MULTI_EXECUTE_TOOL enables batch/destructive operations and there is no explicit post-execution validation/retry feedback loop, so the batch-operation cap holds workflow clarity at 3.

3 / 5

Progressive Disclosure

A single self-contained file (~85 lines) with well-organized sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Pitfalls, Quick Reference) and no nested references; scored 4 rather than 5 because it slightly exceeds the under-50-line simple-skill line and the Quick Reference table duplicates earlier material.

4 / 5

Total

15

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and names a specific, distinguishable niche (Amara via Rube MCP), but it lacks an explicit 'Use when...' trigger clause and offers only generic action language, which limits completeness and trigger-term coverage to mid-range scores.

Suggestions

Add an explicit trigger clause, e.g. 'Use when automating Amara subtitle, caption, or translation tasks via Rube MCP.'

Replace the generic 'Automate Amara tasks' with concrete actions like 'create, edit, and fetch Amara subtitles and translations'.

Include natural synonyms users say (subtitles, captions, translations, Amara videos) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the Amara domain and one concrete procedural action ('search tools first for current schemas'), but 'Automate Amara tasks' is generic and no domain-specific actions (subtitles, translations) are listed, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Provides a clear 'what' (Automate Amara tasks via Rube MCP) but no 'when'/'Use when...' trigger guidance, which per the guidelines caps completeness at 3 for a missing explicit trigger clause.

3 / 5

Trigger Term Quality

'Amara tasks' is a relevant natural trigger, but coverage is thin with no synonyms or common variations (subtitles, captions, translations, Amara videos), fitting the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

Naming both a distinct platform (Amara) and a specific integration (Rube MCP/Composio) gives it a clear niche with minimal conflict risk, though the trigger is not fully elaborated, placing it just below the comprehensive distinctiveness anchor.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
ComposioHQ/awesome-claude-skills
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.