What prerequisites do I need?

Rube MCP connected (RUBE_SEARCH_TOOLS available), an active Feathery connection with the feathery toolkit, and always search tools first for current schemas.

How do I execute a Feathery tool?

Use RUBE_SEARCH_TOOLS to get tool slugs and input schemas, ensure the Feathery connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then run RUBE_MULTI_EXECUTE_TOOL with the tool slug, proper arguments, memory, and a session_id.

feathery-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Feathery Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/feathery

Prerequisites

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

Step 2: Check Connection

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

Overview

Feathery Automation via Rube MCP enables automating Feathery operations using Composio's Feathery toolkit. It requires a connected Rube MCP and an active Feathery connection, and it emphasizes always searching for current tool schemas before execution.

How This Skill Works

This skill orchestrates Feathery tasks by first discovering available tools with RUBE_SEARCH_TOOLS, then validating the Feathery connection with RUBE_MANAGE_CONNECTIONS, and finally executing the chosen tool via RUBE_MULTI_EXECUTE_TOOL. Tools are run in a session, with explicit memory provided and the latest schemas used to form accurate arguments.

When to Use It

Automate repetitive Feathery workflows to save time
When tool schemas change frequently and you must fetch current schemas first
When setting up a new Feathery integration and validating connectivity
When executing multiple Feathery tools in a single session with a shared context
When performing bulk Feathery operations using RUBE_REMOTE_WORKBENCH and run_composio_tool

Quick Start

Step 1: Verify Rube MCP is connected and RUBE_SEARCH_TOOLS responds
Step 2: Manage Feathery connections with toolkits: [feathery] and ensure ACTIVE
Step 3: Discover a tool with RUBE_SEARCH_TOOLS and execute it via RUBE_MULTI_EXECUTE_TOOL using the returned slug and memory

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to get current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running 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 handle pagination if present

Example Use Cases

Automate a daily Feathery task by discovering tools via RUBE_SEARCH_TOOLS, validating connection, and executing a tool with a memory payload in a single session
Set up a new Feathery integration by adding the Feathery toolkit via Rube MCP, checking ACTIVE status, then running a tool with discovered arguments
Orchestrate multi-tool Feathery workflows by reusing a session_id across RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL
Respond to tool schema changes by resuming with fresh schemas from RUBE_SEARCH_TOOLS before each execution
Bulk update Feathery data using RUBE_REMOTE_WORKBENCH and run_composio_tool with discovered tool slugs

Frequently Asked Questions

Add this skill to your agents