ambient-weather-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/ambient-weather-automation --openclawAmbient Weather Automation via Rube MCP
Automate Ambient Weather operations through Composio's Ambient Weather toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/ambient_weather
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Ambient Weather connection via
RUBE_MANAGE_CONNECTIONSwith toolkitambient_weather - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitambient_weather - 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: "Ambient Weather 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 Ambient Weather task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["ambient_weather"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Ambient Weather-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit ambient_weather |
| 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/ambient-weather-automation/SKILL.mdView on GitHub Overview
Automate Ambient Weather operations using Composio's Ambient Weather toolkit via Rube MCP. Always search for current tool schemas first to adapt to changes and ensure correct tool usage.
How This Skill Works
Discover available tools with RUBE_SEARCH_TOOLS to retrieve slugs and input schemas. Ensure the Ambient Weather connection is ACTIVE via RUBE_MANAGE_CONNECTIONS. Then execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying exact schema-compliant arguments and a memory payload, all tied to a session_id that can be reused across the workflow.
When to Use It
- When you need to perform an end-to-end Ambient Weather operation (e.g., read sensor data and trigger actions).
- When tool schemas may change; fetch current schemas before selecting a tool slug.
- When you must confirm the Ambient Weather connection is ACTIVE prior to execution.
- When you want to reuse session IDs across related workflows to optimize state tracking.
- When performing bulk or remote operations using run_composio_tool via the Composio toolkit.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration (no API keys needed).
- Step 2: Run RUBE_SEARCH_TOOLS with use_case set for Ambient Weather tasks to discover available tools and schemas.
- Step 3: Run RUBE_MANAGE_CONNECTIONS for toolkit ambient_weather and, if ACTIVE, execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory, all under a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool slugs and schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results; avoid hardcoding.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow and handle pagination tokens when present.
Example Use Cases
- Pull the latest temperature and humidity, then trigger an alert if thresholds are exceeded.
- Schedule a daily data pull from Ambient Weather and push results to a dashboard.
- Fetch rain or wind readings and automate a corresponding home action (e.g., closing windows).
- Check connection status, retrieve current readings, and update a monitoring log in sequence.
- Run bulk checks by discovering tools and executing multiple ambient_weather tools via remote bench.