Rube MCP is the middleware endpoint (rube.app/mcp) that lets Composio automate Canny tasks through the canny toolkit.

No API keys are needed; you just add the MCP server URL and establish a connection.

Why must I always search tools first?

Tool schemas change over time. RUBE_SEARCH_TOOLS returns the current slugs, input schemas, and execution plans, preventing hardcoded errors.

canny-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Canny Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/canny

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Canny operations through Composio's Canny toolkit using Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS and establishing an ACTIVE Canny connection via RUBE_MANAGE_CONNECTIONS, enabling reproducible, schema-compliant workflows without hardcoding tool slugs.

How This Skill Works

Start by discovering available Canny tools with RUBE_SEARCH_TOOLS to obtain current slugs and input schemas. Next, verify the connection status with RUBE_MANAGE_CONNECTIONS and then execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, supplying memory, session_id, and the schema-compliant arguments. Always fetch fresh schemas before execution to adapt to changes in tool definitions.

When to Use It

Automating routine Canny operations (create/update tasks, add comments)
When tool schemas change and you must avoid hardcoding slugs
Setting up a reusable, multi-step workflow across sessions
Performing bulk operations across multiple Canny tasks
Verifying an ACTIVE connection before running any workflows

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case: 'Canny operations'
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ['canny'] and verify ACTIVE
Step 3: RUBE_MULTI_EXECUTE_TOOL with discovered tool_slug and schema-compliant arguments, including memory and session_id

Best Practices

Always search for tools first to get current schemas
Check that the connection is ACTIVE before executing tools
Use exact field names and types from the discovered schema
Include memory in every RUBE_MULTI_EXECUTE_TOOL call
Reuse session IDs within a workflow and paginate responses if needed

Example Use Cases

Create a new Canny task using a discovered tool slug and schema
Update multiple tasks by iterating discovered tools in a single session
Bulk archive or update several tasks via multi-execute tooling
Sync Canny task fields from an external trigger with schema-compliant arguments
Resume automation in a new run by reusing the previous session_id to maintain context

Frequently Asked Questions

Add this skill to your agents