Do I always need to search tools first?

Yes. The workflow relies on RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas before execution.

How do I verify the Sensibo connection is ready?

Use RUBE_MANAGE_CONNECTIONS with toolkits: ["sensibo"] and check that the session reports ACTIVE.

Can I reuse sessions across steps?

Yes. Reusing session IDs within a workflow is recommended to maintain context, but generate new sessions for separate workflows.

sensibo-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Sensibo Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/sensibo

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Sensibo operations through Composio's Rube MCP toolkit. It highlights discovering current tool schemas before execution to ensure up-to-date capabilities and reliable automation.

How This Skill Works

Begin by discovering available Sensibo tools with RUBE_SEARCH_TOOLS to obtain current tool slugs and input schemas. Then establish or verify an ACTIVE Sensibo connection via RUBE_MANAGE_CONNECTIONS using the sensibo toolkit, and execute tools with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments. Maintain session continuity and memory state, re-fetching schemas if tool lists change.

When to Use It

You need to perform a Sensibo operation but don’t know the exact tool slug or required arguments.
Before running any workflow, verify RUBE_SEARCH_TOOLS responds and the Sensibo connection is ACTIVE.
You want to execute a discovered tool with the correct schema from RUBE_SEARCH_TOOLS.
You’re building a multi-step Sensibo workflow and want to reuse a session ID.
Tool schemas may have changed, so you re-fetch schemas to avoid failures.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS responds to fetch current Sensibo tools and schemas.
Step 3: Use RUBE_MANAGE_CONNECTIONS to connect to the Sensibo toolkit and run RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug and proper arguments.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the discovered schemas.
Include memory: {} in RUBE_MULTI_EXECUTE_TOOL calls.
Reuse sessions within a workflow and handle pagination if tool lists are long.

Example Use Cases

Discover available Sensibo operations with RUBE_SEARCH_TOOLS and execute a simple task using a discovered slug and inputs.
Validate that the Sensibo connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before starting a multi-step workflow.
Reuse a session ID across several steps in a Sensibo automation sequence.
If tool schemas change, re-run RUBE_SEARCH_TOOLS to fetch updated slugs and arguments before execution.
Persist state by supplying a memory object in RUBE_MULTI_EXECUTE_TOOL for a chained task.

Frequently Asked Questions

Add this skill to your agents