home / skills / composiohq / awesome-claude-skills / simple-analytics-automation

simple-analytics-automation skill

/simple-analytics-automation

This skill automates Simple Analytics tasks through Composio's MCP, prioritizing tool discovery before execution to ensure up-to-date schemas and safe

npx playbooks add skill composiohq/awesome-claude-skills --skill simple-analytics-automation

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

Files (1)
SKILL.md
3.0 KB
---
name: simple-analytics-automation
description: "Automate Simple Analytics tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# 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](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `simple_analytics`
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: "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](https://composio.dev)*

Overview

This skill automates Simple Analytics tasks using Composio’s Simple Analytics toolkit via Rube MCP. It orchestrates discovery, connection management, and tool execution patterns so agents can reliably run analytics operations without hardcoding schemas. The workflow emphasizes always searching tools first and validating active connections before execution.

How this skill works

The skill uses Rube MCP endpoints to discover available Simple Analytics tools, verify or establish a toolkit connection, and execute one or more tools with schema-compliant arguments. Typical flow: call RUBE_SEARCH_TOOLS to get tool slugs and input schemas, confirm connection status with RUBE_MANAGE_CONNECTIONS, then invoke RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs) using the discovered schemas and session IDs.

When to use it

  • Automating report generation, metric collection, or data exports from Simple Analytics
  • Integrating Simple Analytics operations into multi-step agent workflows or pipelines
  • Running bulk or scheduled analytics tasks that require remote tool orchestration
  • Building an agent that must adapt to changing tool schemas or multiple tenants
  • When you need safe, schema-driven execution and connection validation before running tools

Best practices

  • Always call RUBE_SEARCH_TOOLS first—never hardcode tool slugs or argument shapes
  • Confirm toolkit connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools
  • Pass exact field names and types returned from the search; follow schemaRef if provided
  • Include an explicit memory object (can be {}) in RUBE_MULTI_EXECUTE_TOOL calls
  • Reuse session_id across a logical workflow; generate a new session for separate runs
  • Handle pagination: check responses for tokens and iterate until results are complete

Example use cases

  • Discover available Simple Analytics exports, then run a daily CSV export job via RUBE_MULTI_EXECUTE_TOOL
  • Check connection status, authorize a new tenant connection, and run a one-off metrics pull
  • Automate a multi-step pipeline that queries pageviews, filters by date, and stores results in a downstream system
  • Bulk-run a list of report generation tools using RUBE_REMOTE_WORKBENCH and run_composio_tool() for throughput
  • Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before building a dynamically generated UI for analytics operations

FAQ

Do I need API keys to use Rube MCP?

No API keys are required. Add https://rube.app/mcp as an MCP server in your client configuration to connect.

What if tool schemas change?

Always run RUBE_SEARCH_TOOLS before execution to retrieve current schemas and recommended execution plans; never rely on hardcoded fields.