teltel-automation

Overview of teltel-automation skill

What teltel-automation does

teltel-automation is a Claude skill for running Teltel operations through Composio’s Rube MCP server. Its core value is not a fixed set of hard-coded actions; it teaches the agent to discover the current Teltel tool schemas first, confirm the user’s Teltel connection, and then execute the right Rube tool with the required inputs.

This matters because MCP tool schemas can change. The skill’s main operating rule is: use RUBE_SEARCH_TOOLS before attempting a Teltel action.

Best-fit users and workflows

The teltel-automation skill is best for users who already use Claude with MCP tools and want a repeatable way to automate Teltel tasks without manually checking Composio documentation each time. It fits operators, support teams, growth teams, and workflow builders who need an AI assistant to help perform Teltel-related actions through an authenticated tool connection.

It is especially useful when your task is specific but the exact Rube tool name or input schema is unknown.

What makes this skill different

Many automation prompts assume tool names and parameters. This skill instead follows a safer discovery-first pattern:

• Verify Rube MCP is available.
• Confirm the teltel toolkit connection is active.
• Search for current Teltel tools and schemas.
• Execute only after the required fields are known.
• Report results and surface tool errors clearly.

That makes teltel-automation more resilient than a generic “automate Teltel” prompt.

Adoption requirements

Before using the teltel-automation skill, you need a client that supports MCP and access to Rube MCP at https://rube.app/mcp. You also need an active Teltel connection through RUBE_MANAGE_CONNECTIONS with toolkit teltel.

The upstream skill contains a single SKILL.md file, so there are no helper scripts, examples folder, or additional rule files to inspect. The decision to install should be based on whether you want this Rube MCP workflow pattern embedded into your assistant.

How to Use teltel-automation skill

teltel-automation install context

Install the skill from the Composio skill collection, then configure Rube MCP in your AI client:

npx skills add ComposioHQ/awesome-claude-skills --skill teltel-automation

Add the MCP server endpoint:

https://rube.app/mcp

After installation, verify that the assistant can access RUBE_SEARCH_TOOLS. If that tool is unavailable, the teltel-automation skill cannot operate correctly because discovery is its first required step.

Connect Teltel before running workflows

Use RUBE_MANAGE_CONNECTIONS with the teltel toolkit and confirm the connection status is ACTIVE. If the connection is not active, follow the returned authorization link and complete setup before asking the assistant to run a business task.

A practical first prompt is:

“Use the teltel-automation skill. Check whether Rube MCP is available, confirm my teltel toolkit connection is active, and do not execute any Teltel action until you have searched for the current tool schema.”

This prevents the assistant from guessing unsupported fields or calling stale tool names.

Turn rough goals into executable prompts

Weak prompt:

“Automate my Teltel task.”

Stronger prompt:

“Use teltel-automation for Workflow Automation. I need to perform this Teltel task: [describe the exact operation]. First call RUBE_SEARCH_TOOLS for that use case, then tell me which tool you found, what required fields it needs, and what information you still need from me. After I confirm, execute the tool and summarize the result.”

This works better because the skill depends on the use case to search relevant tools and build a valid execution plan.

Repository files to read first

For this repository, read composio-skills/teltel-automation/SKILL.md first. It contains the actual workflow contract: prerequisites, setup, tool discovery, connection checking, and execution pattern.

There are no local scripts/, resources/, references/, or README.md files in the skill directory, so the most important external reference is the Composio Teltel toolkit documentation at composio.dev/toolkits/teltel. Use that documentation only as background; at runtime, trust RUBE_SEARCH_TOOLS for current schemas.

teltel-automation skill FAQ

Is teltel-automation only for Claude?

The skill is written for Claude-style skill usage and depends on MCP tool access. The underlying workflow is Rube MCP based, so the practical requirement is an AI client that can load the skill and call MCP tools such as RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS.

What does teltel-automation not do?

It does not bundle custom Teltel scripts, local API clients, or static command-line utilities. It also does not replace Teltel authentication. If the teltel toolkit connection is inactive, the skill should stop and ask you to complete the connection flow.

It should not be used for blind execution where you cannot review required fields or confirm sensitive actions.

Why not use an ordinary prompt?

An ordinary prompt may invent tool names, assume outdated schemas, or skip connection checks. The teltel-automation skill gives the agent a specific operating pattern: discover tools first, validate the Teltel connection, then execute with current schema information. That reduces avoidable tool-call failures and makes the assistant’s behavior easier to audit.

Is this skill beginner-friendly?

It is beginner-friendly if you already have MCP enabled, but it is not a one-click standalone app. New users should start by asking the assistant to verify Rube availability and Teltel connection status before requesting real automation. If MCP setup is unfamiliar, that setup step will be the main blocker, not the skill content itself.

How to Improve teltel-automation skill

Improve teltel-automation results with better inputs

The best inputs include the target operation, the business context, any IDs or records already known, constraints, and whether execution should wait for confirmation.

Good prompt pattern:

“Use teltel-automation. My goal is [specific Teltel outcome]. I have these known fields: [IDs, names, dates, account context]. Search tools first, identify the exact schema, ask for missing required fields, and wait for my approval before executing.”

This gives the agent enough detail to search narrowly and avoid unnecessary back-and-forth.

Common failure modes to watch for

The most common failure is skipping RUBE_SEARCH_TOOLS and trying to call a tool from memory. Another is attempting execution before the teltel connection is active. A third is providing a vague use case, which can return broad or irrelevant tool options.

If the first result looks wrong, ask the assistant to repeat discovery with a more specific use case and include known fields in the search query.

Iterate after the first output

After the assistant discovers a tool, review three things before execution:

• Does the tool match the business action you intended?
• Are all required schema fields present?
• Are there side effects, such as creating, updating, sending, or deleting something?

If anything is unclear, ask for a dry-run explanation: “Before executing, explain the selected Teltel tool, required inputs, expected result, and possible failure cases.”

When to customize the skill

Consider extending the skill if your team repeatedly runs the same Teltel workflow. Useful additions could include approved prompt templates, required confirmation rules for sensitive actions, examples of common Teltel use cases, or organization-specific field naming conventions.

Keep the original discovery-first rule intact. The biggest advantage of teltel-automation is that it adapts to current Rube schemas instead of relying on stale assumptions.