What is fluxguard-automation?

A workflow to automate Fluxguard tasks via Composio's Fluxguard toolkit using Rube MCP.

No API keys are needed. You connect by adding the Rube MCP endpoint and establishing an active Fluxguard connection.

What do I need to run this skill?

Rube MCP connected, an ACTIVE Fluxguard connection, and you must call RUBE_SEARCH_TOOLS first to fetch current schemas. For multi tool execution, include memory and a session_id.

fluxguard-automation

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

Files (1)

SKILL.md

2.9 KB

Fluxguard Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/fluxguard

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Fluxguard operations through Composio's Fluxguard toolkit via Rube MCP. Start by discovering current tool schemas with RUBE_SEARCH_TOOLS, then connect to Fluxguard and execute tasks with RUBE_MULTI_EXECUTE_TOOL.

How This Skill Works

The workflow begins by using RUBE_SEARCH_TOOLS to discover available Fluxguard tool slugs and input schemas. Next, RUBE_MANAGE_CONNECTIONS ensures an ACTIVE Fluxguard connection. Finally, RUBE_MULTI_EXECUTE_TOOL runs the chosen tool with schema-compliant arguments, memory, and a session_id to complete the automation.

When to Use It

You need to automate Fluxguard tasks and reduce manual operations.
Tool schemas change frequently and you must fetch the current slugs before running.
You want to verify an ACTIVE Fluxguard connection before executing tools.
You need to run either a single Fluxguard tool or a batch of tools in one workflow.
You are migrating an existing Fluxguard automation to Composio and want to map to discovered tool slugs.

Quick Start

Step 1: Add the Fluxguard MCP server and verify RUBE_SEARCH_TOOLS responds.
Step 2: Run RUBE_SEARCH_TOOLS to discover tool slugs and schemas.
Step 3: Check activation with RUBE_MANAGE_CONNECTIONS and execute a tool with RUBE_MULTI_EXECUTE_TOOL including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results for tool arguments.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and generate a new one for new workflows.

Example Use Cases

Discover tools for a Fluxguard monitoring task and execute using the discovered tool slug and arguments.
Connect the Fluxguard toolkit and run a recurring Fluxguard workflow with session reuse.
Bulk execute several Fluxguard tasks using RUBE_MULTI_EXECUTE_TOOL and a single session.
Retrieve full tool schemas with RUBE_GET_TOOL_SCHEMAS and then run the best matching tool.
Migrate an existing Fluxguard automation by mapping old tasks to discovered tool slugs.

Frequently Asked Questions

Add this skill to your agents