What is here-automation?

A skill to automate Here tasks through Composio's Here toolkit using Rube MCP.

Why must I search tools first?

Tool schemas change over time; searching ensures you have the latest slugs and argument structures.

How do I verify a successful connection?

Call RUBE_MANAGE_CONNECTIONS with the Here toolkit and confirm the status is ACTIVE before executing any tool.

here-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Here Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/here

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Here operations through Composio's Here toolkit via Rube MCP. It emphasizes discovering current tool schemas first to ensure accurate tool slugs and arguments and to prevent hardcoding. Active connection checks and session reuse keep workflows reliable.

How This Skill Works

Begin by calling RUBE_SEARCH_TOOLS to fetch current Here tool schemas. Next, establish or verify the Here connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, execute the selected tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug, proper arguments, and a memory payload.

When to Use It

When starting a new Here automation, always run RUBE_SEARCH_TOOLS to fetch current tool schemas.
When connecting to the Here toolkit, verify the connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before running workflows.
When selecting a tool, use the exact slug and schema from the search results and provide memory in RUBE_MULTI_EXECUTE_TOOL.
When reusing workflow steps, maintain the same session_id across steps to preserve context.
When tool schemas change or you need full details, fetch full schemas with RUBE_GET_TOOL_SCHEMAS before executing.

Quick Start

Step 1: Verify RUBE MCP configuration and ensure RUBE_SEARCH_TOOLS is available.
Step 2: Discover available Here tools with RUBE_SEARCH_TOOLS and review tool slugs and schemas.
Step 3: Connect (if needed) via RUBE_MANAGE_CONNECTIONS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper arguments, memory, and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any tool to get up-to-date schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before tool execution.
Use exact field names and types from the search results in tool arguments.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow to maintain context and reduce setup steps.

Example Use Cases

Discover tools for a Here use case and execute a specific tool slug with the required arguments from the search results.
Connect to the Here toolkit and verify ACTIVE status before starting a multi-step workflow.
Reuse a single session_id across multiple steps of a Here automation to maintain context.
Handle tool schema changes by re-running RUBE_SEARCH_TOOLS and adjusting arguments accordingly.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate fields before execution.

Frequently Asked Questions

Add this skill to your agents