What is the main prerequisite for using folk-automation?

You must have Rube MCP connected and call RUBE_SEARCH_TOOLS to fetch tool schemas before executing any Folk tools.

How do I ensure tool schemas stay current?

Always run RUBE_SEARCH_TOOLS prior to execution; tool slugs and arguments can change over time.

What if the Folk connection isn't ACTIVE?

Use RUBE_MANAGE_CONNECTIONS to activate the Folk toolkit and then re-check status before running workflows.

folk-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Folk Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/folk

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Folk operations through Composio's Folk toolkit using the Rube MCP integration. It emphasizes discovering current tool schemas first with RUBE_SEARCH_TOOLS and ensuring an ACTIVE Folk connection before running workflows.

How This Skill Works

Connect to Rube MCP by adding the MCP server (e.g., https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS. Use RUBE_SEARCH_TOOLS to discover available Folk tools and their input schemas, then check the Folk connection status with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing the discovered arguments, a memory object (even if empty), and an active session_id.

When to Use It

Automate routine Folk operations and workflows end-to-end.
Always fetch current tool schemas before executing any Folk tool.
Set up or refresh a Folk integration and ensure the connection is ACTIVE.
Reuse session IDs within a single Folk workflow to maintain continuity.
Orchestrate multiple tools in bulk using RUBE_MULTI_EXECUTE_TOOL or related bulk APIs.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'folk' and ensure the connection status is ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch up-to-date tool schemas.
Verify the connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools.
Use exact field names and types from the discovered schemas; avoid hardcoding.
Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow or start a new one for a new task.

Example Use Cases

Discover available Folk tools with RUBE_SEARCH_TOOLS for a Folk operations use case and execute a returned TOOL_SLUG with the provided arguments.
Establish an ACTIVE Folk connection via RUBE_MANAGE_CONNECTIONS, then run a simple tool through RUBE_MULTI_EXECUTE_TOOL.
Coordinate a multi-step Folk workflow by reusing a session_id across steps and executing subsequent tools.
Perform bulk operations using RUBE_REMOTE_WORKBENCH and run_composio_tool() to orchestrate multiple Folk tools.
When tool schemas change, re-run RUBE_SEARCH_TOOLS to obtain the latest slugs and schemas instead of hardcoding.

Frequently Asked Questions

Add this skill to your agents