CtrlK
BlogDocsLog inGet started
Tessl Logo

adyntel-automation

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

75

7.69x
Quality

63%

Does it follow best practices?

Impact

100%

7.69x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/adyntel-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 content is well-structured and actionable with concrete tool-call examples and a useful pitfall/reference layout. Its main weakness is workflow clarity for a batch-execution skill: connection is validated but tool-execution results are not, missing the feedback loop the rubric expects for batch operations.

Suggestions

Add an execution-result validation and retry feedback loop after RUBE_MULTI_EXECUTE_TOOL (check for errors/pagination, retry or surface failures) to lift workflow_clarity above the batch cap.

De-duplicate the RUBE_SEARCH_TOOLS example between the "Tool Discovery" section and "Step 1" to tighten conciseness.

Provide one concrete filled-in execute example (real tool slug + sample arguments) so the execute step is copy-paste ready rather than placeholder-only.

DimensionReasoningScore

Conciseness

The body is lean with code blocks, a pitfall list, and a quick-reference table, with only minor redundancy where the "Tool Discovery" section and "Step 1" both demonstrate RUBE_SEARCH_TOOLS; it could be trimmed slightly but is generally efficient.

4 / 5

Actionability

Concrete RUBE_* tool-call blocks with named parameters and an operation-to-approach table give mostly executable guidance; argument placeholders like "schema-compliant args from search results" are a minor gap, though justified by the dynamic-tool design.

4 / 5

Workflow Clarity

The setup and core workflow are clearly sequenced with an ACTIVE-connection checkpoint, but this batch/automation skill (RUBE_MULTI_EXECUTE_TOOL, bulk ops) lacks an execution-result validation or error-retry feedback loop, so the batch-operation cap of 3 applies.

3 / 5

Progressive Disclosure

A single well-sectioned file with clear headers and one external doc link; with no bundle files to split, structure is good, though the Tool Discovery / Step 1 overlap is a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

57%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 clear about what it does and highly distinctive, but it lacks an explicit use-when trigger clause and does not enumerate specific Adyntel operations or natural user synonyms. It sits at a competent-but-generic midpoint with strong distinctiveness.

Suggestions

Add an explicit 'Use when...' clause naming concrete Adyntel task types (e.g., scheduling, reporting, contact sync) to lift completeness and trigger_term_quality.

Expand the action list from the generic 'Automate Adyntel tasks' to a few specific operations to improve specificity.

Include natural user phrasings or synonyms alongside the Adyntel proper noun to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Automate Adyntel tasks via Rube MCP (Composio)" names the domain and the "search tools first for current schemas" behavior, but enumerates no specific Adyntel operations, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

The "what" is clear ("Automate Adyntel tasks via Rube MCP"), but there is no "Use when..." clause or equivalent trigger guidance; per the rubric a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

"Adyntel" is a strong specific keyword, but the description offers no natural synonyms, variations, or task-type phrases a user might say, fitting the anchor with some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

"Adyntel" is a distinctive proper-noun niche tied to a specific toolkit, giving a clear niche with minimal conflict risk against other skills.

5 / 5

Total

14

/

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.