home / skills / composiohq / awesome-claude-skills / cutt-ly-automation

cutt-ly-automation skill

/cutt-ly-automation

This skill automates Cutt Ly tasks through Rube MCP, always discovering current tool schemas before execution to ensure accuracy.

npx playbooks add skill composiohq/awesome-claude-skills --skill cutt-ly-automation

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

Files (1)
SKILL.md
2.9 KB
---
name: cutt-ly-automation
description: "Automate Cutt Ly tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# 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](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cutt_ly`
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: "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](https://composio.dev)*

Overview

This skill automates Cutt Ly tasks by orchestrating Composio's Cutt Ly toolkit through Rube MCP. It provides a reliable pattern for discovering tools, validating connections, and executing schema-compliant operations. The goal is repeatable, safe automation that adapts to changing tool schemas.

How this skill works

The skill always begins by calling RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and recommended execution plans. It then confirms an active Cutt Ly connection via RUBE_MANAGE_CONNECTIONS and runs operations using RUBE_MULTI_EXECUTE_TOOL (including an explicit memory payload and session ID). The workflow enforces schema compliance, session reuse, and pagination handling to avoid errors from stale assumptions.

When to use it

  • When you need programmatic access to Cutt Ly functionality from an agent or automation pipeline
  • Before executing any Composio/Cutt Ly operation that depends on dynamic tool schemas
  • When running bulk or chained Cutt Ly tasks that require session continuity
  • When integrating Cutt Ly operations into larger Rube MCP-driven workflows

Best practices

  • Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and recommended args
  • Verify the Cutt Ly connection shows ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools
  • Include a memory object (even if empty) in RUBE_MULTI_EXECUTE_TOOL calls
  • Reuse session IDs for related operations; generate new ones for separate workflows
  • Respect field names and types exactly as returned; handle pagination tokens until complete

Example use cases

  • Discovering available Cutt Ly endpoints and their input schemas before running a task
  • Connecting and authenticating a Cutt Ly toolkit for an automated publishing pipeline
  • Executing a sequence of Cutt Ly operations in a single session with RUBE_MULTI_EXECUTE_TOOL
  • Running bulk content updates using RUBE_REMOTE_WORKBENCH and run_composio_tool()
  • Fetching full tool schemas with RUBE_GET_TOOL_SCHEMAS to build validation logic

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; no API keys are required for basic connectivity.

What happens if tool schemas change?

Always re-run RUBE_SEARCH_TOOLS before executing; do not hardcode slugs or arguments. Adjust calls to match the returned schema exactly.