Amplitude Automation

PassAudited by ClawScan on May 10, 2026.

Overview

This is a coherent Amplitude automation skill, but it can use a connected Amplitude account through Rube MCP to read and change analytics data.

Install this only if you intend to let the agent operate on Amplitude through Rube MCP. Before running write workflows, verify the Amplitude workspace, user IDs, cohort IDs, and payloads, and disconnect the integration when you no longer need it.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

The agent could change Amplitude analytics data or cohort membership if the user asks it to perform those workflows.

Why it was flagged

The skill documents tools that can write analytics events and change cohort membership. This is purpose-aligned for Amplitude automation, but these are account-mutating actions.

Skill content
`AMPLITUDE_SEND_EVENTS` - Send one or more events to Amplitude ... `AMPLITUDE_UPDATE_COHORT_MEMBERSHIP` - Add/remove users from a cohort
Recommendation

Confirm the exact project, users, event payloads, and cohort changes before allowing write actions, especially for bulk updates.

What this means

The connected account determines what Amplitude data the agent can read or modify.

Why it was flagged

The skill requires an authenticated Amplitude connection through Rube. This is expected for the stated purpose, but it grants delegated account access.

Skill content
Active Amplitude connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `amplitude` ... follow the returned auth link to complete Amplitude authentication
Recommendation

Use the least-privileged Amplitude account or workspace available, and revoke the Rube connection when it is no longer needed.

What this means

Requests and relevant Amplitude task data may pass through Rube/Composio as part of tool execution.

Why it was flagged

The skill routes tool discovery and Amplitude actions through an external MCP service. This is disclosed and central to the skill, but it introduces a third-party data and permission boundary.

Skill content
Add `https://rube.app/mcp` as an MCP server in your client configuration.
Recommendation

Only connect this MCP server if you trust the provider and understand what Amplitude permissions the connection grants.