home / skills / composiohq / awesome-claude-skills / customgpt-automation

customgpt-automation skill

safe

/customgpt-automation

This skill automates Customgpt tasks through Rube MCP, ensuring up-to-date tool schemas are discovered before execution for reliable workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill customgpt-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: customgpt-automation
description: "Automate Customgpt tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Customgpt Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["customgpt"]
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 Customgpt-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `customgpt` |
| 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 Customgpt tasks through Composio's Customgpt toolkit using Rube MCP. It provides a reliable pattern for discovering tool schemas, managing toolkit connections, and executing multi-tool workflows safely. The workflow emphasizes dynamic discovery and schema compliance to avoid broken automation.

How this skill works

First call RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and execution guidance. Then verify or establish an active Customgpt connection via RUBE_MANAGE_CONNECTIONS. Finally run actions using RUBE_MULTI_EXECUTE_TOOL (including a memory object) or orchestrate bulk runs with RUBE_REMOTE_WORKBENCH.

When to use it

Automating Customgpt operations that require up-to-date tool schemas
Running multi-step workflows across Composio tools via Rube MCP
Building repeatable integrations that must validate connection state first
Performing bulk or remote workbench runs for batch processing
Orchestrating tool chains where schema changes are likely

Best practices

Always call RUBE_SEARCH_TOOLS first — tool schemas and slugs change frequently
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE for the customgpt toolkit before executing
Supply the exact field names and types returned by the search results; don’t hardcode inputs
Include a memory object (even if empty {}) with RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs inside a workflow; generate new session IDs for separate workflows
Handle pagination tokens when searching tools or listing results

Example use cases

Discover available Customgpt actions, then run an automated content generation pipeline
Validate and refresh a Customgpt connection before scheduled workflow runs
Batch-process many prompts using RUBE_REMOTE_WORKBENCH and run_composio_tool() for throughput
Build a monitoring job that searches for schema changes and alerts on incompatible fields
Chain several Composio tools discovered at runtime to transform data and publish outputs

FAQ

Do I need API keys to use Rube MCP?

No API keys are required; add https://rube.app/mcp as an MCP server in your client configuration and the MCP endpoint works.

What if a tool slug changes after I hardcoded it?

If you hardcode slugs you risk failures. Always run RUBE_SEARCH_TOOLS at the start of a workflow to obtain current slugs and schemas.