$ ~/registry/skill/composiohq-composio-skills-adyntel-automation

SKILL

adyntel-automation

Name: adyntel-automation
Author: Composio

Automate Adyntel tasks through Rube MCP using current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be an open-source prompt-only wrapper and does not directly require local code installation or static API keys, so its baseline risk is relatively low. However, real use depends on remote Rube MCP and an external Adyntel connection, which introduces network egress and third-party authorization considerations.

CredentialsCaution

The material says 'No API keys needed,' but the workflow requires establishing an `adyntel` connection via `RUBE_MANAGE_CONNECTIONS` and following a returned auth link when the connection is not ACTIVE. So while there are no static environment variables, third-party OAuth or account tokens may still be involved, creating a normal credential exposure surface.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to operate Adyntel tools. User task descriptions, session data, tool arguments, and execution results are therefore likely sent to that remote service and its integration chain. No unrelated or obviously undisclosed endpoints are shown, but there is clear third-party network egress.

Code executionLow risk

Based on the provided material, this skill itself is prompt-only documentation/workflow guidance. It does not ship local scripts, binaries, or direct shell execution steps; any execution capability resides mainly in the external MCP/tools rather than in the skill itself.

Data accessCaution

The skill text itself does not claim local file or system access, but its workflow sends 'your specific Adyntel task,' session IDs, memory, and tool arguments to the remote MCP, which then operates through the connected Adyntel toolkit. This creates a normal access surface for user-provided business data and remote account data, with no evidence here of excessive local permissions beyond the stated purpose.

Supply chainLow risk

The source is a GitHub open-source repository with strong community adoption (64.7k stars), both of which are significant risk-reducing signals. The material also looks more like an auditable skill description than a closed-source executable payload. The missing license declaration and unknown maintenance status are worth noting, but they are not enough on their own to justify a high-risk rating.

Recommendations

Enable it only after verifying trust in `rube.app/mcp` and the relevant privacy terms, and avoid sending unnecessary sensitive business content.
Use a least-privilege account when authorizing Adyntel, and regularly review and revoke connections that are no longer needed.
Before first use, review the Composio/Adyntel tool documentation to confirm what data is transmitted, how long it is retained, and who processes it.
If possible, test this skill in an isolated workspace before connecting it to highly sensitive accounts or data.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "adyntel-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/adyntel-automation/SKILL.md
2. Save it as ~/.claude/skills/adyntel-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Adyntel Automation via Rube MCP

Automate Adyntel operations through Composio's Adyntel toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/adyntel

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Adyntel connection via RUBE_MANAGE_CONNECTIONS with toolkit adyntel
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit adyntel
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Adyntel operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Adyntel task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["adyntel"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Adyntel-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `adyntel`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Automate Yandex tasks and workflows through Rube MCP integrations.

ComposioGet→

$ loading_