Why should I always search tools first?

Tool schemas change over time. Searching with RUBE_SEARCH_TOOLS ensures you use current slugs and argument names instead of hardcoding values.

How can I tell if the connection to Simple Analytics is ready?

Use RUBE_MANAGE_CONNECTIONS to check the toolkit connection status and ensure it reports ACTIVE before running any tools.

Do I have to include memory in every tool execution?

Yes. Memory must be included in RUBE_MULTI_EXECUTE_TOOL calls, even if it's an empty object, to maintain session state.

simple-analytics-automation

Scanned

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

Files (1)

SKILL.md

3.0 KB

Simple Analytics Automation via Rube MCP

Automate Simple Analytics operations through Composio's Simple Analytics toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/simple_analytics

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["simple_analytics"]
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 Simple Analytics-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `simple_analytics`
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/simple-analytics-automation/SKILL.md

View on GitHub

Overview

This skill automates Simple Analytics tasks using Composio's Rube MCP and the Simple Analytics toolkit. It always searches for current tool schemas, ensures an active connection, and executes discovered tools, making analytics workflows resilient to changes.

How This Skill Works

The workflow starts by calling RUBE_SEARCH_TOOLS to fetch available tools and their input schemas. Next, it uses RUBE_MANAGE_CONNECTIONS to ensure the Simple Analytics connection is ACTIVE. Finally, it runs the selected tool through RUBE_MULTI_EXECUTE_TOOL, providing a memory object and the discovered tool slug within a shared session.

When to Use It

When you need to automate routine Simple Analytics tasks without hardcoding tool slugs, relying on current schemas.
When tool schemas or available tools update and you must fetch fresh descriptors before execution.
When establishing or validating an active Simple Analytics connection prior to workflows.
When you want to reuse a single session across multiple analytics steps to improve efficiency.
When performing bulk analytics operations that involve executing multiple tools in sequence.

Quick Start

Step 1: Connect to Rube MCP and verify RUBE_SEARCH_TOOLS responds.
Step 2: Manage the Simple Analytics connection with RUBE_MANAGE_CONNECTIONS and ensure ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a tool via RUBE_MULTI_EXECUTE_TOOL in a shared session.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding slugs.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({ }).
Reuse session IDs within a workflow and generate new ones for new tasks.

Example Use Cases

Schedule a daily export of key metrics from Simple Analytics by discovering the appropriate tool and executing it within an active session.
Chain multiple analytics transforms (e.g., funnel and retention checks) in a single session using discovered tool slugs.
Automatically update dashboards by running transformation tools after pulling fresh data.
After a tool update, revalidate schemas by running RUBE_SEARCH_TOOLS before executing any tasks.
Perform bulk analytics by issuing several RUBE_MULTI_EXECUTE_TOOL calls in one session to complete a batch of tasks.

Frequently Asked Questions

Add this skill to your agents