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

chatfai-automation skill

safe

/chatfai-automation

This skill automates Chatfai tasks via Rube MCP, consistently discovering tool schemas before execution to ensure up-to-date, reliable workflows.

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

# Chatfai Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["chatfai"]
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 Chatfai-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `chatfai` |
| 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 Chatfai tasks through Composio's Chatfai toolkit using the Rube MCP control plane. It guides discovery of current tool schemas, manages Chatfai connections, and runs Composio tools reliably. The workflow enforces session reuse, schema compliance, and memory inclusion to avoid runtime errors.

How this skill works

Always call RUBE_SEARCH_TOOLS first to discover available tool slugs, input schemas, and recommended execution plans. Use RUBE_MANAGE_CONNECTIONS to ensure the Chatfai toolkit connection is ACTIVE, then run tools via RUBE_MULTI_EXECUTE_TOOL or bulk ops with RUBE_REMOTE_WORKBENCH. The skill emphasizes reading returned schemas, supplying exact fields, including a memory object, and reusing session IDs for a consistent workflow.

When to use it

Automating repeated Chatfai operations across projects or environments
When you need programmatic access to Chatfai toolsets exposed via Composio
Before executing any Composio tool to ensure schemas and slugs are current
When orchestrating multi-step workflows that require session state and memory
For bulk or parallel Chatfai tasks using RUBE_REMOTE_WORKBENCH

Best practices

Always call RUBE_SEARCH_TOOLS first; never hardcode tool slugs or input shapes
Verify RUBE_MANAGE_CONNECTIONS returns ACTIVE for toolkit chatfai before execution
Supply schema-compliant arguments exactly as returned by tool discovery
Always include a memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow; create a new session for new workflows
Handle pagination tokens returned by searches and fetch until complete

Example use cases

Discover available Chatfai tools and programmatically run a text-generation tool in a production workflow
Initialize and verify a Chatfai connection as part of CI checks before automated runs
Batch-run data enrichment or conversation tasks via RUBE_REMOTE_WORKBENCH and run_composio_tool()
Build an orchestration that chains Composio tool outputs using RUBE_MULTI_EXECUTE_TOOL with memory
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before generating validated request payloads

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client; no API keys are required for the MCP endpoint.

What if a tool schema changes during a workflow?

Always re-run RUBE_SEARCH_TOOLS for the latest schema. If a schema changes mid-workflow, regenerate or validate arguments against the new schema before executing.