aryn-automation
Automate Aryn tasks via Rube MCP (Composio). Always search tools first for current schemas.
67
Quality
53%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./composio-skills/aryn-automation/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too vague and lacks essential information for skill selection. It names specific tools (Aryn, Rube MCP, Composio) but fails to explain what tasks can be automated or when this skill should be used. The procedural instruction about searching tools is internal guidance rather than a capability description.
Suggestions
Add specific concrete actions that can be performed (e.g., 'Parse documents, extract tables, run document processing pipelines via Aryn')
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user mentions Aryn, document parsing, or needs to process documents through Composio')
Explain what Aryn/Rube MCP/Composio actually do so Claude can match user requests that don't use these exact product names
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate Aryn tasks' without specifying what concrete actions can be performed. 'Always search tools first' is procedural guidance, not a capability description. | 1 / 3 |
Completeness | The 'what' is extremely vague ('Automate Aryn tasks') and there is no 'when' clause or explicit trigger guidance. The description fails to answer either question adequately. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('Aryn', 'Rube MCP', 'Composio') but these are technical/product names rather than natural terms users would say. Missing common variations or task-oriented language. | 2 / 3 |
Distinctiveness Conflict Risk | The specific product names (Aryn, Rube MCP, Composio) provide some distinctiveness, but 'automate tasks' is generic enough to potentially conflict with other automation skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently communicates how to automate Aryn tasks via Rube MCP. The workflow is clear with proper validation checkpoints, and the Known Pitfalls section adds valuable guardrails. The main weakness is that the tool call examples use a pseudocode-like format rather than showing actual executable syntax, which slightly reduces actionability.
Suggestions
Show one complete, executable example of a real Aryn operation end-to-end (e.g., actual tool slug and real argument values) to demonstrate the full pattern
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what Aryn or Composio are. | 3 / 3 |
Actionability | Provides concrete tool call patterns with specific parameters, but the examples are pseudocode-like structures rather than fully executable code. The argument placeholders and comments reduce copy-paste readiness. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequence (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-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. Quick reference table provides at-a-glance navigation. External link to toolkit docs is one level deep and clearly signaled. | 3 / 3 |
Total | 11 / 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 | |
- Repository
- ComposioHQ/awesome-claude-skills
- Commit
2790447
- 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.