Skip to main content
skill CX Codex

amplitude-automation — Claude Code skill: automate analytics

amplitude-automation connects Amplitude to your IDE via Rube MCP and Composio. Send events, search users, manage cohorts without leaving the editor.

MIT 131 installs ★ 3,785 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add davepoon/buildwithclaude --skill amplitude-automation -a claude-code
Open on GitHub

What amplitude-automation does

The skill bridges your IDE and Amplitude API through Rube MCP, a remote context protocol layer. Start by adding https://rube.app/mcp as an MCP server in your client config, then install the skill. Five core workflows ship: event transmission (AMPLITUDE_SEND_EVENTS), user activity history (AMPLITUDE_GET_USER_ACTIVITY), user lookup and property updates (AMPLITUDE_FIND_USER, AMPLITUDE_IDENTIFY), cohort operations (LIST, GET, UPDATE_MEMBERSHIP), and event schema browsing.

Key constraints: events need either user_id or device_id. Timestamps go in milliseconds from epoch (13 digits), not seconds. Fetching activity requires calling AMPLITUDE_FIND_USER first to convert your app's user_id into Amplitude's internal ID—skipping this step silently fails. Cohort membership changes run async; poll status via CHECK_COHORT_STATUS using the request_id from the response.

The skill demands an active Amplitude connection through Rube (RUBE_MANAGE_CONNECTIONS) and recommends calling RUBE_SEARCH_TOOLS upfront to get the latest tool schemas. If Amplitude auth is pending, Rube returns a link to complete it.

What it helps with

  • track events in Amplitude from code or prompts
  • look up a user by ID and review their event stream
  • set or modify user properties with Amplitude operations
  • list, inspect, and update cohort membership
  • sync analytics between your IDE and Amplitude

Example prompts for the agent

  • Send purchase events to Amplitude with user_id [email protected] and event_type purchase
  • Find user by email and show their last 50 events in reverse chronological order
  • Add all users from the vip cohort to a new enterprise segment

How to install amplitude-automation

1Skills CLI (Vercel)

npx skills add davepoon/buildwithclaude --skill amplitude-automation -a claude-code

2Manually: put the files in place

~/.claude/skills/amplitude-automation/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/amplitude-automation/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about amplitude-automation

How do I install amplitude-automation for Claude Code?

Run npx skills add davepoon/buildwithclaude --skill amplitude-automation -a claude-code, then open ~/.claude/skills/amplitude-automation/SKILL.md. Ensure your IDE config includes the MCP server https://rube.app/mcp first.

What are the prerequisites for amplitude-automation?

You need Rube MCP (added as https://rube.app/mcp in your client config), an active Amplitude connection via Rube, and access to the Composio Amplitude toolkit. Auth credentials flow through Rube's interface.

Why doesn't GET_USER_ACTIVITY find events after I send them?

Always call AMPLITUDE_FIND_USER first with your application's user_id—it translates to Amplitude's internal ID, which GET_USER_ACTIVITY requires. Also, events process asynchronously and may not be queryable for a few seconds.

Source text

SKILL.md · MIT
---
name: amplitude-automation
description: "Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas."
requires:
  mcp: [rube]
category: analytics
---

# Amplitude Automation via Rube MCP

Automate Amplitude product analytics through Composio's Amplitude toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/amplitude](https://composio.dev/toolkits/amplitude)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Amplitude connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `amplitude`
- 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 `amplitude`
3. If connection is not ACTIVE, follow the returned auth link to complete Amplitude authentication
4. Confirm connection status shows ACTIVE before running any workflows

## Core Workflows

### 1. Send Events

**When to use**: User wants to track events or send event data to Amplitude

**Tool sequence**:
1. `AMPLITUDE_SEND_EVENTS` - Send one or more events to Amplitude [Required]

**Key parameters**:
- `events`: Array of event objects, each containing:
  - `event_type`: Name of the event (e.g., 'page_view', 'purchase')
  - `user_id`: Unique user identifier (required if no `device_id`)
  - `device_id`: Device identifier (required if no `user_id`)
  - `event_properties`: Object with custom event properties
  - `user_properties`: Object with user properties to set
  - `time`: Event timestamp in milliseconds since epoch

**Pitfalls**:
- At least one of `user_id` or `device_id` is required per event
- `event_type` is required for every event; cannot be empty
- `time` must be in milliseconds (13-digit epoch), not seconds
- Batch limit applies; check schema for maximum events per request
- Events are processed asynchronously; successful API response does not mean data is immediately queryable

### 2. Get User Activity

**When to use**: User wants to view event history for a specific user

**Tool sequence**:
1. `AMPLITUDE_FIND_USER` - Find user by ID or property [Prerequisite]
2. `AMPLITUDE_GET_USER_ACTIVITY` - Retrieve user's event stream [Required]

**Key parameters**:
- `user`: Amplitude internal user ID (from FIND_USER)
- `offset`: Pagination offset for event list
- `limit`: Maximum number of events to return

**Pitfalls**:
- `user` parameter requires Amplitude's internal user ID, NOT your application's user_id
- Must call FIND_USER first to resolve your user_id to Amplitude's internal ID
- Activity is returned in reverse chronological order by default
- Large activity histories require pagination via `offset`

### 3. Find and Identify Users

**When to use**: User wants to look up users or set user properties

**Tool sequence**:
1. `AMPLITUDE_FIND_USER` - Search for a user by various identifiers [Required]
2. `AMPLITUDE_IDENTIFY` - Set or update user properties [Optional]

**Key parameters**:
- For FIND_USER:
  - `user`: Search term (user_id, email, or Amplitude ID)
- For IDENTIFY:
  - `user_id`: Your application's user identifier
  - `device_id`: Device identifier (alternative to user_id)
  - `user_properties`: Object with `$set`, `$unset`, `$add`, `$append` operations

**Pitfalls**:
- FIND_USER searches across user_id, device_id, and Amplitude ID
- IDENTIFY uses special property operations (`$set`, `$unset`, `$add`, `$append`)
- `$set` overwrites existing values; `$setOnce` only sets if not already set
- At least one of `user_id` or `device_id` is required for IDENTIFY
- User property changes are eventually consistent; not immediate

### 4. Manage Cohorts

**When to use**: User wants to list cohorts, view cohort details, or update cohort membership

**Tool sequence**:
1. `AMPLITUDE_LIST_COHORTS` - List all saved cohorts [Required]
2. `AMPLITUDE_GET_COHORT` - Get detailed cohort information [Optional]
3. `AMPLITUDE_UPDATE_COHORT_MEMBERSHIP` - Add/remove users from a cohort [Optional]
4. `AMPLITUDE_CHECK_COHORT_STATUS` - Check async cohort operation status [Optional]

**Key parameters**:
- For LIST_COHORTS: No required parameters
- For GET_COHORT: `cohort_id` (from list results)
- For UPDATE_COHORT_MEMBERSHIP:
  - `cohort_id`: Target cohort ID
  - `memberships`: Object with `add` and/or `remove` arrays of user IDs
- For CHECK_COHORT_STATUS: `request_id` from update response

**Pitfalls**:
- Cohort IDs are required for all cohort-specific operations
- UPDATE_COHORT_MEMBERSHIP is asynchronous; use CHECK_COHORT_STATUS to verify
- `request_id` from the update response is needed for status checking
- Maximum membership changes per request may be limited; chunk large updates
- Only behavioral cohorts support API membership updates

### 5. Browse Event Categories

**When to use**: User wants to discover available event types and categories in Amplitude

**Tool sequence**:
1. `AMPLITUDE_GET_EVENT_CATEGORIES` - List all event categories [Required]

**Key parameters**:
- No required parameters; returns all configured event categories

**Pitfalls**:
- Categories are configured in Amplitude UI; API provides read access
- Event names within categories are case-sensitive
- Use these categories to validate event_type values before sending events

## Common Patterns

### ID Resolution

**Application user_id -> Amplitude internal ID**:
```
1. Call AMPLITUDE_FIND_USER with user=your_user_id
2. Extract Amplitude's internal user ID from response
3. Use internal ID for GET_USER_ACTIVITY
```

**Cohort name -> Cohort ID**:
```
1. Call AMPLITUDE_LIST_COHORTS
2. Find cohort by name in results
3. Extract id for cohort operations
```

### User Property Operations

Amplitude IDENTIFY supports these property operations:
- `$set`: Set property value (overwrites existing)
- `$setOnce`: Set only if property not already set
- `$add`: Increment numeric property
- `$append`: Append to list property
- `$unset`: Remove property entirely

Example structure:
```json
{
  "user_properties": {
    "$set": {"plan": "premium", "company": "Acme"},
    "$add": {"login_count": 1}
  }
}
```

### Async Operation Pattern

For cohort membership updates:
```
1. Call AMPLITUDE_UPDATE_COHORT_MEMBERSHIP -> get request_id
2. Call AMPLITUDE_CHECK_COHORT_STATUS with request_id
3. Repeat step 2 until status is 'complete' or 'error'
```

## Known Pitfalls

**User IDs**:
- Amplitude has its own internal user IDs separate from your application's
- FIND_USER resolves your IDs to Amplitude's internal IDs
- GET_USER_ACTIVITY requires Amplitude's internal ID, not your user_id

**Event Timestamps**:
- Must be in milliseconds since epoch (13 digits)
- Seconds (10 digits) will be interpreted as very old dates
- Omitting timestamp uses server receive time

**Rate Limits**:
- Event ingestion has throughput limits per project
- Batch events where possible to reduce API calls
- Cohort membership updates have async processing limits

**Response Parsing**:
- Response data may be nested under `data` key
- User activity returns events in reverse chronological order
- Cohort lists may include archived cohorts; check status field
- Parse defensively with fallbacks for optional fields

## Quick Reference

| Task | Tool Slug | Key Params |
|------|-----------|------------|
| Send events | AMPLITUDE_SEND_EVENTS | events (array) |
| Find user | AMPLITUDE_FIND_USER | user |
| Get user activity | AMPLITUDE_GET_USER_ACTIVITY | user, offset, limit |
| Identify user | AMPLITUDE_IDENTIFY | user_id, user_properties |
| List cohorts | AMPLITUDE_LIST_COHORTS | (none) |
| Get cohort | AMPLITUDE_GET_COHORT | cohort_id |
| Update cohort members | AMPLITUDE_UPDATE_COHORT_MEMBERSHIP | cohort_id, memberships |
| Check cohort status | AMPLITUDE_CHECK_COHORT_STATUS | request_id |
| List event categories | AMPLITUDE_GET_EVENT_CATEGORIES | (none) |

---
*Powered by [Composio](https://composio.dev)*

© davepoon · MIT · davepoon/buildwithclaude

Similar skills

All skills for Automation and no-code: n8n, Zapier, Make →

From the same set235

The whole set →
agent-analytics Sets up lightweight web analytics, funnels, and A/B experiments via CLI. Gives AI agents direct access to traffic metrics and conversion data across projects. CX Codex +1 137installs oiloil-ui-ux-guide oiloil-ui-ux-guide is a Claude Code skill that gives interface design guidance or reviews an existing UI with prioritized fixes. CX Codex +1 134installs ios-hig-design-guide ios-hig-design-guide is a Claude Code skill that turns Apple Human Interface Guidelines into specs for iOS features. It activates for questions about UI rules, accessibility, components, or interaction patterns. CX Codex +1 133installs google-drive-automation google-drive-automation — a skill that automates Google Drive workflows: uploads and downloads files, searches documents, creates folders, and manages permissions. Runs via Rube MCP and Composio with an active Google Drive connection. CX Codex +1 133installs google-analytics-automation google-analytics-automation automates Google Analytics 4 reporting and property inspection through the Rube MCP server. CX Codex +1 130installs activecampaign-automation activecampaign-automation automates ActiveCampaign contacts, tags, subscriptions, and tasks directly from your coding agent via Rube MCP. CX Codex +1 128installs googlesheets-automation googlesheets-automation — a skill for automating Google Sheets: read and write data, manage tabs, format cells, filter and search rows. Connects via Rube MCP and requires active Google authentication. CX Codex +1 128installs discord-automation discord-automation automates Discord messaging, roles, webhooks, and reactions using Rube MCP and Composio toolkits. It lets AI coding agents manage Discord channels and bot workflows directly. CX Codex +1 128installs

Project sponsors

Companies that keep this analytics open