adyntel-automation

Automate Adyntel operations and workflows through the Rube MCP gateway.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill adyntel-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adyntel-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/adyntel-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill adyntel-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead of navigating Adyntel interfaces by providing a standardized, automated way to discover and execute tools via the Rube MCP gateway.

Core Features & Use Cases

  • Tool Discovery: Dynamically fetch current schemas and execution plans for Adyntel operations.
  • Connection Management: Handle authentication and session state for secure, persistent tool access.
  • Workflow Execution: Execute multi-step operations using discovered tool slugs and schema-compliant arguments.

Quick Start

Use the adyntel-automation skill to search for available tools and execute a workflow for your specific task.

Frequently Asked Questions about adyntel-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover available Adyntel tools?

Call the RUBE_SEARCH_TOOLS function with a specific use case query to retrieve current tool slugs, input schemas, and recommended execution plans for your Adyntel tasks.

How do I verify my Adyntel connection status?

Use the RUBE_MANAGE_CONNECTIONS command with the 'adyntel' toolkit parameter to check if your connection is active before attempting to execute any tools.

Why must I call RUBE_SEARCH_TOOLS before executing?

Tool schemas and arguments in the Adyntel toolkit are subject to change. Searching first ensures you use the most current, valid schema to prevent execution errors.

Can I reuse session IDs for different workflows?

You should reuse session IDs within a single, continuous workflow to maintain state, but generate new session IDs for distinct, unrelated workflows to ensure clean execution.