$ ~/registry/skill/composiohq-composio-skills-conversion-tools-automation

SKILL

conversion-tools-automation

Name: conversion-tools-automation
Author: Composio

Automate file and format conversion tasks via Rube MCP with schema lookup first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is essentially a prompt/instruction wrapper for operating Rube MCP / Composio conversion tools, with open-source distribution and strong community trust signals. The main concern is not the skill text itself, but that it directs users to connect to a remote MCP service and execute external tools, so the overall posture is low to moderate concern.

CredentialsCaution

The material claims 'no API keys needed', but it also requires activating a `conversion_tools` connection via `RUBE_MANAGE_CONNECTIONS` and following an auth link, which implies third-party OAuth or connection authorization at runtime. No direct request for local high-sensitivity secrets is shown, but the external authorization scope should be reviewed.

Network egressCaution

The README explicitly instructs users to add `https://rube.app/mcp` as an MCP server and to search/execute tools through Composio/Rube; therefore user inputs, session IDs, tool arguments, and possibly business data may be sent to that remote service. No additional unknown endpoint is shown, but this conflicts with the metadata claiming no remote endpoint and warrants attention to actual data flows.

Code executionLow risk

Based on the provided material, the skill itself is a prompt/workflow description and does not contain local scripts, install commands, or direct code execution logic. While downstream MCP tools may perform remote tool actions, this skill text does not declare local process spawning or system-level execution permissions.

Data accessCaution

The instructions require reusing sessions, passing `memory`, and querying schemas/executing tools through a remote MCP, indicating that task context and invocation parameters may be handled by an external service. There is no direct request for local filesystem read/write access, nor evidence of local data access beyond the stated 'conversion tools automation' scope.

Supply chainLow risk

The source is an open GitHub repository with high community adoption (64.7k stars), which materially lowers supply-chain risk. The material shows no obfuscated install script, suspicious dependencies, or obvious injection content; the remaining gaps are the undeclared license and unknown maintenance status, so repository activity and release practices should still be verified before production use.

Recommendations

Treat `rube.app/mcp` as a real outbound data path and verify its privacy policy, logging retention, and data handling scope before connecting.
Apply least privilege when authorizing `RUBE_MANAGE_CONNECTIONS`, enabling only the scopes required for the conversion task.
Do not send unnecessary sensitive data in tool search, schema discovery, or execution arguments; prefer redacted or sample data for testing.
Before production use, verify repository maintenance activity, license status, and the official documentation/domain ownership of Composio/Rube.

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 "conversion-tools-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/conversion-tools-automation/SKILL.md
2. Save it as ~/.claude/skills/conversion-tools-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Conversion Tools Automation via Rube MCP

Automate Conversion Tools operations through Composio's Conversion Tools toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/conversion_tools

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["conversion_tools"]
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 Conversion Tools-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `conversion_tools`
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 curated workflows with Rube MCP after checking current tool schemas first.

ComposioGet→

$ loading_