home / skills / composiohq / awesome-claude-skills / bolt-iot-automation

bolt-iot-automation skill

safe

/bolt-iot-automation

This skill automates Bolt IoT tasks via Rube MCP by discovering current tool schemas before execution to ensure accurate, up-to-date workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill bolt-iot-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: bolt-iot-automation
description: "Automate Bolt Iot tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Bolt Iot Automation via Rube MCP

Automate Bolt Iot operations through Composio's Bolt Iot toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/bolt_iot](https://composio.dev/toolkits/bolt_iot)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Bolt Iot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bolt_iot`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bolt_iot`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Bolt Iot 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 Bolt Iot task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["bolt_iot"]
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 Bolt Iot-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bolt_iot` |
| 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](https://composio.dev)*

Overview

This skill automates Bolt IoT operations by orchestrating Composio's Bolt Iot toolkit through a Rube MCP connection. It guides tool discovery, connection checks, and schema-compliant execution so workflows run reliably. Always perform tool discovery first to use current schemas and avoid hardcoded arguments.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to retrieve available tool slugs, input schemas, execution plans, and pagination tokens. It validates or establishes a bolt_iot connection via RUBE_MANAGE_CONNECTIONS, then runs actions using RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs) with schema-compliant arguments and a session ID. Memory must be included in execute calls and session IDs should be reused per workflow.

When to use it

Automate sensor reads, device control, and telemetry collection for Bolt IoT devices.
Run scheduled or triggered Bolt IoT tasks from an agent or orchestration pipeline.
Perform bulk device operations or batch updates across many devices.
Integrate Bolt IoT actions into larger automation workflows that require schema-driven tool calls.
Validate and test Bolt IoT command schemas before production runs.

Best practices

Always call RUBE_SEARCH_TOOLS first — tool schemas and slugs can change frequently.
Confirm RUBE_MANAGE_CONNECTIONS shows ACTIVE for the bolt_iot toolkit before executing any tools.
Use exact field names and types returned by search results; do not hardcode argument structures.
Include a memory object (even empty {}) in RUBE_MULTI_EXECUTE_TOOL calls.
Reuse session IDs across steps in a single workflow and generate new IDs for separate workflows.
Handle pagination tokens from search responses and continue fetching until all tools or schemas are retrieved.

Example use cases

Discover available Bolt IoT device commands and list required fields before sending a control command.
Verify and activate a bolt_iot connection, then read sensor telemetry for a specific device and store results.
Run bulk firmware or configuration updates using RUBE_REMOTE_WORKBENCH with run_composio_tool().
Compose a multi-step workflow: search tools → confirm connection → toggle device GPIO → read-back status.
Automate scheduled telemetry collection and forward parsed metrics to monitoring or alerting systems.

FAQ

What if RUBE_SEARCH_TOOLS returns no results?

Confirm the Rube MCP connection is reachable, check pagination, and ensure the bolt_iot toolkit is available; re-run search with a broader use_case string.

Do I need API keys for Rube MCP?

No API keys are required to add the Rube MCP endpoint; just include https://rube.app/mcp in your client configuration, but toolkit-specific auth may be required during connection setup.

Can I hardcode tool slugs and argument shapes?

No. Tool slugs and schemas change. Always fetch current schemas with RUBE_SEARCH_TOOLS and use the returned field names and types.