How do I ensure schemas are current?

Always call RUBE_SEARCH_TOOLS before using any tool; tool slugs and argument names can change.

What if the connection isn't ACTIVE?

Follow the auth link from RUBE_MANAGE_CONNECTIONS to complete setup, then re-check status.

Do I need to include memory in execute calls?

Yes; include memory: {} even if empty to satisfy memory parameter requirement.

influxdb-cloud-automation

Scanned

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

Files (1)

SKILL.md

3.0 KB

Influxdb Cloud Automation via Rube MCP

Automate Influxdb Cloud operations through Composio's Influxdb Cloud toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/influxdb_cloud

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["influxdb_cloud"]
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 Influxdb Cloud-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `influxdb_cloud`
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/influxdb-cloud-automation/SKILL.md

View on GitHub

Overview

This skill automates Influxdb Cloud operations through Composio’s Rube MCP toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution to stay aligned with the latest capabilities.

How This Skill Works

First, connect Rube MCP and verify an active influxdb_cloud connection via RUBE_MANAGE_CONNECTIONS. Then run RUBE_SEARCH_TOOLS to fetch current tool slugs and schemas, select a tool, and finally execute it with RUBE_MULTI_EXECUTE_TOOL using the provided memory payload and schema-compliant arguments.

When to Use It

Automating routine Influxdb Cloud tasks (queries, writes, and bucket management).
When tool schemas may change and you must fetch the latest slugs before running workflows.
When you need to confirm the Influxdb Cloud connection is ACTIVE before executing tools.
When reusing session IDs to maintain context across a multi-step workflow.
When performing bulk or multi-tool operations that require discovered tool slugs and schemas.

Quick Start

Step 1: Ensure RUBE_SEARCH_TOOLS responds to discover current tool schemas.
Step 2: Call RUBE_MANAGE_CONNECTIONS to activate the influxdb_cloud toolkit and verify ACTIVE.
Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory payload.

Best Practices

Always call RUBE_SEARCH_TOOLS before any execution.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before running tools.
Use exact field names and types from the tool schemas returned by search.
Include memory: {} in every RUBE_MULTI_EXECUTE_TOOL call.
Reuse session IDs within a workflow and avoid creating new sessions unnecessarily.

Example Use Cases

Discover tools and run a data backfill task in Influxdb Cloud.
Execute a sequence of queries to populate a dashboard after a schema change.
Create and run a bucket-management workflow across multiple tools.
Bulk export data to another system via a composed tool chain.
Validate results after applying updates to Influxdb Cloud configurations.

Frequently Asked Questions

Add this skill to your agents