What is cardly-automation?

A workflow to automate Cardly tasks via Rube MCP and Composio.

Do I need to hardcode tool slugs?

No, always search tool schemas with RUBE_SEARCH_TOOLS.

What if the tool schemas change?

Re-run RUBE_SEARCH_TOOLS to obtain updated slugs and schemas.

cardly-automation

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

Files (1)

SKILL.md

2.8 KB

Cardly Automation via Rube MCP

Automate Cardly operations through Composio's Cardly toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/cardly

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Cardly operations through Composio's Cardly toolkit using Rube MCP. It requires an active RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS setup with the Cardly toolkit and an active Cardly connection. Always fetch current tool schemas before running any workflow.

How This Skill Works

Technically, you first query available Cardly tools with RUBE_SEARCH_TOOLS to obtain slugs and input schemas. Then verify or establish the Cardly connection with RUBE_MANAGE_CONNECTIONS and confirm the status is ACTIVE. Finally execute a tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug, proper arguments, memory, and session_id.

When to Use It

Automating Cardly operations end-to-end via Rube MCP and the Cardly toolkit
Before every run, call RUBE_SEARCH_TOOLS to fetch current tool schemas
Ensure the Cardly connection is ACTIVE using RUBE_MANAGE_CONNECTIONS before executing tools
Coordinate multiple Cardly tools in a single session with RUBE_MULTI_EXECUTE_TOOL
Adapt workflows safely when tool schemas change; avoid hardcoding slugs

Quick Start

Step 1: Verify RUBE_SEARCH_TOOLS is available and returns tool slugs
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit cardly and confirm ACTIVE
Step 3: Discover a tool via RUBE_SEARCH_TOOLS and run it using RUBE_MULTI_EXECUTE_TOOL with memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before execution
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE
Use exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow, but generate new ones for new workflows

Example Use Cases

Automate a Cardly update task by discovering TOOL_SLUGS and executing with the right args
Batch process several Cardly operations in a single session
Migrate Cardly automation by fetching latest tool schemas instead of hardcoding slugs
Regularly verify ACTIVE connection before each Cardly run
Use RUBE_REMOTE_WORKBENCH to run multiple Cardly actions in bulk

Frequently Asked Questions

Add this skill to your agents