adyntel-automation

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

7.69x

Quality

53%

Does it follow best practices?

Impact

100%

7.69x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./composio-skills/adyntel-automation/SKILL.md

Quality

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 components for effective skill selection. It names specific tools/products but fails to explain what concrete actions the skill performs or when Claude should use it. The description reads more like an internal note than a functional skill description.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user mentions Adyntel, Composio integration, or needs to automate workflows via Rube MCP'

Replace 'Automate Adyntel tasks' with specific concrete actions, e.g., 'Create workflows, sync data between systems, trigger automated actions in Adyntel'

Remove the procedural instruction ('Always search tools first') from the description field - this belongs in the skill body, not the selection-focused description

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'Automate Adyntel tasks' without specifying what concrete actions are performed. 'Search tools first for current schemas' is a procedural instruction, not a capability description.	1 / 3
Completeness	The 'what' is extremely vague ('Automate Adyntel tasks') and there is no 'Use when...' clause or equivalent trigger guidance. The description fails to answer either question adequately.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('Adyntel', 'Rube MCP', 'Composio') but these are technical/product names rather than natural terms users would say. Missing common variations or user-facing language.	2 / 3
Distinctiveness Conflict Risk	The specific product names (Adyntel, 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 guides Claude through Adyntel automation via Rube MCP. The workflow is clear with proper validation checkpoints, and the content respects token budget. The main weakness is that the tool call examples use a pseudo-notation rather than showing actual executable code in a specific language/format.

Suggestions

Clarify the exact format for tool calls - are these JSON payloads, function calls, or another format? Show one complete executable example.

Add an example of handling a failed connection status (what the auth link looks like, how to retry after completing auth).

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding explanations of basic concepts. Every section serves a purpose with no padding or unnecessary context about what Adyntel or Composio are.	3 / 3
Actionability	Provides concrete tool call patterns with field names and structure, but uses pseudo-code notation rather than actual executable code. The examples show the shape of calls but aren't copy-paste ready for any specific runtime.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint (verify ACTIVE status before proceeding) 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. External reference to toolkit docs is one level deep and clearly signaled. Quick reference table aids navigation.	3 / 3
	Total	11 / 12 Passed

Validation

90%

Warnings & errors only

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: 29 days ago

Table of Contents

Discovery Implementation Validation

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.