home / skills / composiohq / awesome-claude-skills / simla-com-automation

simla-com-automation skill

safe

/simla-com-automation

This skill automates Simla Com tasks via Rube MCP by discovering current tool schemas before execution to ensure up-to-date workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill simla-com-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: simla-com-automation
description: "Automate Simla Com tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Simla Com Automation via Rube MCP

Automate Simla Com operations through Composio's Simla Com toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/simla_com](https://composio.dev/toolkits/simla_com)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Simla Com connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `simla_com`
- 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.

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

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Simla Com 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 Simla Com task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["simla_com"]
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 Simla Com-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `simla_com` |
| 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](https://composio.dev)*

Overview

This skill automates Simla Com tasks through Composio's Simla Com toolkit using the Rube MCP. It provides a clear workflow pattern: discover tools, verify connection, then execute schema-compliant tool calls. The skill emphasizes always searching for current tool schemas before running any operation.

How this skill works

First call RUBE_SEARCH_TOOLS to retrieve available tool slugs, input schemas, execution plans, and pagination info. Next verify an active Simla Com connection via RUBE_MANAGE_CONNECTIONS. Finally run one or more tools with RUBE_MULTI_EXECUTE_TOOL (including a memory object and proper session_id) or use RUBE_REMOTE_WORKBENCH for bulk operations.

When to use it

When you need to script or automate Simla Com operations from an agent or CI pipeline
When tool schemas may change and dynamic discovery is required
When performing bulk or batched actions that require session reuse and pagination
When orchestrating multi-step workflows that require connection checks and stateful memory
When you must ensure exact schema compliance for API arguments

Best practices

Always call RUBE_SEARCH_TOOLS first and use returned schemas and tool_slugs; never hardcode arguments or slugs
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for toolkit simla_com before execution
Include a memory object (can be empty {}) on every RUBE_MULTI_EXECUTE_TOOL call
Reuse session_id within a workflow; generate a new session for distinct workflows
Handle pagination tokens from search results and tool responses until completion

Example use cases

Discover available Simla Com operations and generate a schema-compliant execution plan
Run a sequence of Simla Com calls to update configurations or push data using RUBE_MULTI_EXECUTE_TOOL
Execute bulk jobs via RUBE_REMOTE_WORKBENCH and run_composio_tool() for large batch workflows
Automate connection setup checks and prompt for auth flow if RUBE_MANAGE_CONNECTIONS returns a non-ACTIVE status
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS when deep validation or UI generation is needed

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; the MCP flow does not require API keys.

What if a tool schema changes during a workflow?

Always re-run RUBE_SEARCH_TOOLS as needed and validate the schema before calling the tool. Handle schema validation errors gracefully and regenerate arguments from the latest schema.