What are the prerequisites for Klipfolio automation?

RUBE MCP must be connected (RUBE_SEARCH_TOOLS available) and an active Klipfolio connection must exist via RUBE_MANAGE_CONNECTIONS with the toolkit set to klipfolio.

What should I do if a tool slug or schema changes?

Always search for tools first using RUBE_SEARCH_TOOLS to get current slugs and schemas; do not hardcode values.

How do I obtain the full tool schemas?

Use RUBE_GET_TOOL_SCHEMAS for tools with schemaRef to retrieve complete input definitions.

klipfolio-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Klipfolio Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/klipfolio

Prerequisites

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

Step 2: Check Connection

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

Overview

Klipfolio Automation via Rube MCP lets you control Klipfolio operations through Composio’s Klipfolio toolkit. It relies on discovering current tool schemas with RUBE_SEARCH_TOOLS before executing workflows and requires an ACTIVE Klipfolio connection. Follow the setup and workflow steps to reliably orchestrate Klipfolio tasks.

How This Skill Works

The flow starts by discovering available Klipfolio tools using RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Next, you verify or establish a connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, you execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a memory payload; bulk operations can be performed with RUBE_REMOTE_WORKBENCH when needed.

When to Use It

You need to discover current Klipfolio tool schemas before running a workflow.
You must verify or establish an ACTIVE Klipfolio connection via RUBE_MANAGE_CONNECTIONS before execution.
You want to execute a Klipfolio tool using a discovered slug and correct arguments.
You need to perform bulk Klipfolio operations using RUBE_REMOTE_WORKBENCH for efficiency.
You want to fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS to verify Klipfolio tool availability and fetch schemas.
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkits: ["klipfolio"], then RUBE_MULTI_EXECUTE_TOOL with the chosen tool slug and proper arguments.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get updated tool schemas; never hardcode slugs.
Check that RUBE_MANAGE_CONNECTIONS reports an ACTIVE status before executing tools.
Use exact field names and types from the search results when constructing arguments.
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and generate new ones for separate workflows.

Example Use Cases

Discover Klipfolio tools with RUBE_SEARCH_TOOLS, then run a specific tool slug to refresh a dashboard tile.
Establish a Klipfolio connection via RUBE_MANAGE_CONNECTIONS and execute a tool that updates a dataset.
Execute multiple Klipfolio tools in a single session using RUBE_MULTI_EXECUTE_TOOL with discovered slugs.
Use RUBE_REMOTE_WORKBENCH to run bulk Klipfolio operations across several dashboards.
Fetch full schemas with RUBE_GET_TOOL_SCHEMAS to confirm input fields before integration changes.

Frequently Asked Questions

Add this skill to your agents