Automate Bolt Iot tasks via Rube MCP (Composio). Always search tools first for current schemas.
cd ~/.claude/skills
git clone https://github.com/ComposioHQ/awesome-claude-skills.git awesome-claude-skills mkdir -p ~/.claude/skills/bolt-iot-automation
curl -fsSL https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/HEAD/composio-skills/bolt-iot-automation/SKILL.md \
-o ~/.claude/skills/bolt-iot-automation/SKILL.md Automate Bolt Iot operations through Composio’s Bolt Iot toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/bolt_iot
RUBE_MANAGE_CONNECTIONS with toolkit bolt_iotRUBE_SEARCH_TOOLS first to get current tool schemasGet 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.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit bolt_iotAlways 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.
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Bolt Iot task"}]
session: {id: "existing_session_id"}
RUBE_MANAGE_CONNECTIONS
toolkits: ["bolt_iot"]
session_id: "your_session_id"
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
RUBE_SEARCH_TOOLSRUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing toolsmemory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})| 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
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when executing implementation plans with independent tasks in the current session
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when creating new skills, editing existing skills, or verifying skills work before deployment