CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aryn-automation

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

52

Quality

66%

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/aryn-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 skill body is well-structured and actionable with concrete MCP call templates, but it carries some redundancy across its discovery/workflow sections and lacks an explicit error-recovery feedback loop for batch tool execution. Tightening the repeated search examples and adding a validate/retry step would lift the weaker dimensions.

Suggestions

Consolidate the three RUBE_SEARCH_TOOLS demonstrations into one canonical example to remove redundancy and improve conciseness.

Add an explicit feedback loop after RUBE_MULTI_EXECUTE_TOOL (e.g., 'On error, re-run RUBE_SEARCH_TOOLS for the tool, fix arguments, and retry') to raise workflow_clarity above 3.

Expand the bulk-ops Quick Reference entry with a concrete RUBE_REMOTE_WORKBENCH run_composio_tool() example to close the actionability gap.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes Claude's competence, but RUBE_SEARCH_TOOLS is demonstrated three times and the Quick Reference table overlaps the Core Workflow steps, introducing redundancy that could be tightened.

3 / 5

Actionability

Concrete MCP call blocks with real parameters (queries, session, toolkits, tool_slug, arguments, memory) and an operation-to-tool mapping table give mostly executable guidance, with minor gaps like placeholder slugs and an un-expanded bulk-op example.

4 / 5

Workflow Clarity

A clear numbered Setup sequence and a 3-step Core Workflow exist with some checkpoints ('Confirm connection ACTIVE before running'), but RUBE_MULTI_EXECUTE_TOOL is a batch operation without an explicit validate/fix/retry feedback loop, which caps workflow_clarity at 3.

3 / 5

Progressive Disclosure

Content is short and cleanly sectioned (Prerequisites, Setup, Tool Discovery, Core Workflow, Pitfalls, Quick Reference) with no nested or buried references and no need for external files, matching the simple-skill exception for a well-organized overview.

5 / 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 clearly states what the skill does and ties it to a specific niche, but it omits explicit 'Use when...' trigger guidance and lists only one real action, capping completeness and specificity at mid-level. Adding concrete trigger phrases and a fuller action list would lift it toward the top anchors.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user wants to automate Aryn document-processing tasks or asks about Aryn via Composio') to raise completeness above 3.

Enumerate 2-3 concrete actions (e.g., 'Run Aryn partitioning/extraction jobs, manage job status, retrieve results') to move specificity toward 4-5.

Include natural trigger synonyms or variations (e.g., 'Aryn jobs, Aryn extraction, Aryn partitioning') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the Aryn domain and a concrete action ('Automate Aryn tasks') plus a process directive ('Always search tools first for current schemas'), but does not enumerate several specific actions as the 4/5 anchors require.

3 / 5

Completeness

The 'what' is clear ('Automate Aryn tasks via Rube MCP (Composio)') but there is no 'Use when...' or equivalent trigger guidance; 'Always search tools first' is a how-directive, not a when, so completeness caps at 3 per the missing-trigger rule.

3 / 5

Trigger Term Quality

Includes the relevant proper-noun keywords ('Aryn tasks', 'Rube MCP', 'Composio') but offers no synonyms, common variations, or file-extension-style triggers a user would naturally vary.

3 / 5

Distinctiveness Conflict Risk

The Aryn-via-Rube-MCP/Composio niche is fairly distinct from other skills with only minor overlap risk, though the action wording ('Automate Aryn tasks') remains somewhat generic.

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.

Validation — 15 / 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

Path

composio-skills/aryn-automation/SKILL.md

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.