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

plain-automation skill

safe

/plain-automation

This skill automates Plain tasks via Rube MCP, always discovering current tool schemas to streamline workflow execution.

npx playbooks add skill composiohq/awesome-claude-skills --skill plain-automation

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

Files (1)

SKILL.md

2.8 KB

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

# Plain Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["plain"]
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 Plain-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `plain` |
| 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 Plain tasks by orchestrating Composio’s Plain toolkit through the Rube MCP gateway. It guides tool discovery, connection checks, and schema-compliant execution to run Plain operations reliably. The workflow emphasizes always searching tools first and managing session and memory parameters for predictable results.

How this skill works

The skill queries RUBE_SEARCH_TOOLS to discover current tool slugs, input schemas, recommended plans, and pagination info. It ensures an active Plain connection via RUBE_MANAGE_CONNECTIONS and then runs one or more tools with RUBE_MULTI_EXECUTE_TOOL, including a memory object and a session id. It also supports bulk operations through RUBE_REMOTE_WORKBENCH and fetching full schemas with RUBE_GET_TOOL_SCHEMAS when needed.

When to use it

Automate recurring Plain operations across accounts or environments
Run multi-step Plain workflows that require current tool schemas
Perform bulk or batched Plain actions via the remote workbench
Build integrations that must validate toolkit connections before execution
Execute schema-sensitive tasks where field names and types must match exactly

Best practices

Always call RUBE_SEARCH_TOOLS first — tool schemas and slugs can change
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the plain toolkit before executing
Use exact field names and types from the search response; don’t hardcode inputs
Include a memory object (even empty) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs for a single workflow; generate new sessions for new workflows
Handle pagination and follow continuation tokens when listing tools or schemas

Example use cases

Discover Plain tools for a specific business use case and run the recommended execution plan
Connect a new Plain account and validate the ACTIVE status before starting automation
Execute a sequence of Plain operations in one RUBE_MULTI_EXECUTE_TOOL call using discovered tool slugs
Run bulk Plain updates using RUBE_REMOTE_WORKBENCH and composio run_composio_tool()
Fetch a tool’s full schema with RUBE_GET_TOOL_SCHEMAS to build a precise caller-side payload

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 to connect.

What if a tool schema changes mid-workflow?

Always call RUBE_SEARCH_TOOLS before executing any tool to get the current schema. If schemas change, update your arguments and revalidate before execution.