Do I always need to search tools first?

Yes. RUBE_SEARCH_TOOLS retrieves current tool schemas, which can change. Do not hardcode slugs or arguments.

How do I verify Fibery connectivity before running tools?

Use RUBE_MANAGE_CONNECTIONS with the fibery toolkit and ensure the connection status is ACTIVE before executing tools.

What should I include when executing a tool?

Use the exact schema-compliant arguments from the search results and include memory in the RUBE_MULTI_EXECUTE_TOOL call, even if it's an empty object.

fibery-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Fibery Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/fibery

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Fibery operations using Composio's Fibery toolkit via Rube MCP. It requires a connected Rube MCP and an active Fibery connection, and it emphasizes discovering current tool schemas before running workflows.

How This Skill Works

The workflow starts by calling RUBE_SEARCH_TOOLS to fetch available Fibery tool schemas, then verifies the Fibery connection with RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL using schema-compliant arguments. This approach avoids hardcoding slugs and keeps tooling up to date.

When to Use It

When you need to automate a Fibery operation and want to fetch current tool schemas first.
When establishing or validating a Fibery connection within a workflow.
When you have a discovered tool slug and want to run it with correct arguments.
When handling large or paginated results that require repeated tool calls.
When you want to avoid hardcoding tool names by always discovering tools before execution.

Quick Start

Step 1: Add Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Discover Tools: Run RUBE_SEARCH_TOOLS to fetch available Fibery tool schemas (use_case: Fibery operations).
Step 3: Connect and Execute: Run RUBE_MANAGE_CONNECTIONS with toolkit fibery, then RUBE_MULTI_EXECUTE_TOOL using a discovered tool slug and memory: {}.

Best Practices

Always call RUBE_SEARCH_TOOLS before any workflow to get the latest tool schemas.
Validate that the Fibery connection is ACTIVE with RUBE_MANAGE_CONNECTIONS before executing tools.
Use exact field names and types from the tool schemas; avoid hardcoding slugs or arguments.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Bulk update Fibery records by discovering the appropriate tool and applying changes via RUBE_MULTI_EXECUTE_TOOL.
Create new Fibery records from an external CSV feed by selecting a create-tool discovered at runtime.
Sync deal or project statuses from another system into Fibery using a mapped, discovered tool.
Generate a daily Fibery activity report by executing a discovery tool and aggregating results.
Archive completed tasks in Fibery using a bulk operation while handling pagination tokens.

Frequently Asked Questions

Add this skill to your agents