home / skills / composiohq / awesome-claude-skills / apitemplate-io-automation

apitemplate-io-automation skill

safe

/apitemplate-io-automation

This skill automates Apitemplate IO tasks via Rube MCP, ensuring tool schemas are discovered first and connections are active before execution.

npx playbooks add skill composiohq/awesome-claude-skills --skill apitemplate-io-automation

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

Files (1)

SKILL.md

3.0 KB

---
name: apitemplate-io-automation
description: "Automate Apitemplate IO tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Apitemplate IO Automation via Rube MCP

Automate Apitemplate IO operations through Composio's Apitemplate IO toolkit via Rube MCP.

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

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Apitemplate IO connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `apitemplate_io`
- 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 `apitemplate_io`
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: "Apitemplate IO 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 Apitemplate IO task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["apitemplate_io"]
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 Apitemplate IO-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `apitemplate_io` |
| 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 Apitemplate IO tasks by driving Composio's Apitemplate IO toolkit through a Rube MCP connection. It centralizes discovery, connection management, and execution patterns so workflows run reliably against current tool schemas. It enforces searching tools first, validating connections, and using schema-compliant arguments.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to discover available Apitemplate IO tools and their exact input schemas. It then verifies an active toolkit connection with RUBE_MANAGE_CONNECTIONS and runs operations through RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH using the discovered tool slugs and arguments. The workflow always includes session handling and a memory parameter and follows pagination and schema references when present.

When to use it

Automating template generation, updates, or batch exports in Apitemplate IO
Orchestrating multi-step Apitemplate IO workflows that require multiple toolkit calls
Integrating Apitemplate IO actions into larger agent or CI/CD pipelines
Running bulk operations or remote workbench jobs that require Composio tooling
When tool schemas may change and you need dynamic discovery before execution

Best practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs, input schemas, and execution plans
Verify the Apitemplate IO connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing any tool
Use exact field names and types from the search response; never hardcode argument shapes
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}), and reuse session IDs for a workflow
Handle pagination tokens in responses and use RUBE_GET_TOOL_SCHEMAS for full schema details when needed

Example use cases

Discovering available Apitemplate IO endpoints and executing a template render with schema-compliant arguments
Performing bulk template updates via RUBE_REMOTE_WORKBENCH run_composio_tool() jobs
Combining multiple Apitemplate IO calls in a session to create, modify, and export templates
Embedding Apitemplate IO automation inside an agent that first searches tools and then executes safe operations

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 endpoint works without additional API keys for MCP access.

What if a tool schema changes mid-workflow?

Always re-run RUBE_SEARCH_TOOLS when starting a new workflow or before invoking unknown tool slugs. Validate schemas and adjust arguments to match the returned shape.