$ ~/registry/skill/composiohq-composio-skills-files-com-automation

SKILL

files-com-automation

Name: files-com-automation
Author: Composio

Automate Files.com file management and transfer tasks through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill itself is an open-source prompt-only document with no direct local secret requirement or embedded execution logic, so the static artifact is low risk overall. However, it is designed to connect users to remote Rube MCP and a third-party Files.com toolchain, so actual use involves external service access and remote tool invocation that warrants attention to data egress and authorization scope.

CredentialsCaution

The material says 'No API keys needed,' but it also requires establishing an ACTIVE `files_com` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth link, which indicates third-party account authorization/tokens are still involved, just managed by the external platform. This creates ordinary OAuth/connection-token misuse and scope-visibility concerns.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to discover and execute Files.com-related tools. User task arguments, session IDs, and potentially file-operation metadata are expected to be sent to that remote service. The endpoint is declared in the docs, so this is normal external connectivity for such a tool, but data does leave the local environment.

Code executionLow risk

Based on the provided artifact, this is a prompt-style skill document with no executable script, install command, or local process-launch instruction. It describes using external MCP tools for remote operations rather than directly executing code on the local machine.

Data accessCaution

The skill is intended to 'Automate Files Com operations' and mentions execution, bulk operations, and pagination, indicating expected access to remote data resources such as files/directories within a Files.com account. The material does not show least-privilege scope or concrete data boundaries, so it should be treated as having ordinary broad operational access to third-party file data and should be authorized carefully.

Supply chainLow risk

The source is an open-source GitHub repository with high community adoption (64.7k stars), which are strong risk-reducing factors. The provided skill content is also short and auditable. Caveats remain: no declared license, unknown maintenance status, and reliance on external Rube/Composio services that are not audited in this material, but the current facts do not justify a high-risk rating.

Recommendations

Only connect after confirming trust in `rube.app/mcp` and the Composio service, and review their privacy/data-handling documentation.
Use a least-privilege Files.com account or restricted scopes when authorizing, and avoid unnecessary file read/write/admin permissions.
Verify tool names and parameters returned by `RUBE_SEARCH_TOOLS` before execution to avoid sending sensitive content to irrelevant tools.
Test bulk operations and pagination behavior first in a test account or isolated dataset.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "files-com-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/files-com-automation/SKILL.md
2. Save it as ~/.claude/skills/files-com-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Documint document generation and processing tasks through Rube MCP.

ComposioGet→

$ loading_