Do I need API keys to use this skill?

No. Get Rube MCP endpoint and call RUBE_SEARCH_TOOLS; no API keys are required.

Why must I search tools first?

Tool schemas change over time; always fetch current slugs and input schemas before execution.

What if the connection shows not ACTIVE?

Follow the provided auth link via RUBE_MANAGE_CONNECTIONS to complete setup and then recheck for ACTIVE.

files-com-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/files-com-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Files Com Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/files_com

Prerequisites

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

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

Tool Discovery

Always discover available tools before executing workflows:

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["files_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 Files Com-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `files_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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/files-com-automation/SKILL.mdView on GitHub

Overview

Automate Files Com operations through Composio's Files Com toolkit using Rube MCP. This skill emphasizes discovering current tool schemas first and maintaining an ACTIVE connection before executing workflows.

How This Skill Works

You first discover available tools with RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Then you verify the connection to the files_com toolkit via RUBE_MANAGE_CONNECTIONS and activate it if needed. Finally, you execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory object and the required arguments.

When to Use It

You need to automate a Files Com operation and tool schemas change frequently
You want to run a recurring Files Com task using the latest tool slugs and schemas
You must ensure an ACTIVE Files Com connection before executing any tools
You are building a multi-step workflow that discovers tools, validates the connection, then executes
You need to handle pagination or large tool lists when discovering available tools

Quick Start

Step 1: Add the MCP endpoint https://rube.app/mcp as an MCP server in your client configuration and verify RUBE_SEARCH_TOOLS
Step 2: Call RUBE_MANAGE_CONNECTIONS with the toolkit files_com and set the connection to ACTIVE (auth if required)
Step 3: Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and the required arguments, including memory

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas before any run
Check that the Files Com connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools
Pass exact field names and types from the discovered tool schemas; do not hardcode slugs or args
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if it is empty
Reuse session IDs within a workflow and avoid creating new sessions for every step

Example Use Cases

Discover the latest Files Com tools, select a slug for listing files, and execute with the appropriate folder input
Validate an active connection to Files Com, then run a tool to fetch metadata for a batch of files
Synchronize a local folder with Files Com by discovering the upload tool and invoking it with file details
Orchestrate a multi-step automation: discover tools, confirm connection, and run a move or copy operation
Debug a workflow by listing tools, confirming ACTIVE connection, and logging tool responses for auditing

Frequently Asked Questions

Add this skill to your agents