Do I always need an active connection?

Yes, you must have an ACTIVE connection (RUBE_MANAGE_CONNECTIONS) before executing tools.

What if tool schemas change?

Always run RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas; do not hardcode.

How should memory be used?

Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.

cutt-ly-automation

npx machina-cli add skill ComposioHQ/awesome-claude-skills/cutt-ly-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Cutt Ly Automation via Rube MCP

Automate Cutt Ly operations through Composio's Cutt Ly toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/cutt_ly

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["cutt_ly"]
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 Cutt Ly-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `cutt_ly`
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/cutt-ly-automation/SKILL.mdView on GitHub

Overview

Automates Cutt Ly operations through Composio's Cutt Ly toolkit via Rube MCP. This skill emphasizes discovering current tool schemas first and validating an ACTIVE connection before running workflows.

How This Skill Works

First, search for available tools with RUBE_SEARCH_TOOLS to fetch slugs and schemas. Then establish or confirm an ACTIVE connection for the cutt_ly toolkit using RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered arguments and memory, tied to the current session.

When to Use It

When tool schemas change and you need current slugs and inputs
When automating recurring Cutt Ly tasks (bulk or scheduled workflows)
When verifying an ACTIVE connection before executing tools
When you must use exact field names and types from the updated schemas
When reusing session IDs across a workflow and managing memory state

Quick Start

Step 1: Discover available tools with RUBE_SEARCH_TOOLS for Cutt Ly tasks
Step 2: Connect to the toolkit with RUBE_MANAGE_CONNECTIONS and ensure ACTIVE
Step 3: Execute a tool using RUBE_MULTI_EXECUTE_TOOL with memory and session

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Example 1: Shorten a URL by discovering the Cutt Ly tool slug and executing with the required inputs
Example 2: Update a batch of 50 links by discovering tools, connecting, and executing in a loop
Example 3: Adapt to a schema change by re-fetching tool schemas before execution
Example 4: Perform multiple Cutt Ly actions in a single session to reuse context
Example 5: Paginate tool listings to fetch all available Cutt Ly operations

Frequently Asked Questions

Add this skill to your agents