Skills amplitude-automation
📦

amplitude-automation

Content revision r1 Medium Risk ⚙️ External commands🌐 Network access

Automate Amplitude Workflows

Amplitude workflows require careful tool lookup, ID resolution, and status checks. This skill guides Claude, Codex, and Claude Code through Rube MCP tool sequences for common Amplitude tasks.

Supports: Claude Codex Code(CC)
⚠️ 50 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "amplitude-automation" from https://skillstore.io/skills/sickn33-amplitude-automation.md and its manifest at https://skillstore.io/api/skills/sickn33-amplitude-automation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-amplitude-automation.md Signed manifest GET /api/skills/sickn33-amplitude-automation/manifest Signed lockfile GET /api/skills/sickn33-amplitude-automation/lockfile

Test it

Using "amplitude-automation". Find recent activity for user 12345.

Expected outcome:

The assistant first resolves the application ID to an Amplitude internal ID, then returns recent events with pagination guidance.

Using "amplitude-automation". Add these users to the beta cohort.

Expected outcome:

The assistant lists cohorts, confirms the target cohort, requests approval, submits the membership update, and checks completion status.

Using "amplitude-automation". Send a purchase event for a test user.

Expected outcome:

The assistant checks the current schema, validates required identifiers and timestamp format, then asks before sending the event.

Security Audit

Medium Risk
v7 • 7/9/2026 Open versioned report

Most static findings are false positives caused by Markdown backticks, Amplitude IDs, and tool names in documentation. The real risks are the external Rube MCP dependency and write-capable Amplitude actions that can affect analytics data, user properties, and cohorts. No evidence of shell execution, host reconnaissance, or prompt injection was found in SKILL.md.

1
Files scanned
226
Lines analyzed
1
Review items
0
False positives ignored

Confirmed security concerns (2)

Medium
SKILL.md:15-21
Third-Party MCP Data Exposure
The skill instructs users to route Amplitude workflows through Rube MCP. User IDs, event data, cohort details, and analytics metadata may pass through that external service.
The setup and prerequisites explicitly require Rube MCP and an active Amplitude connection. The workflow scope shows analytics data and operations are handled through that connection.
Medium
SKILL.md:31-36SKILL.md:73-79SKILL.md:96-104
Write-Capable Amplitude Operations
The skill includes workflows that can send events, update user properties, and change cohort membership. These actions can affect analytics integrity and audience targeting.
The cited workflows explicitly invoke AMPLITUDE_SEND_EVENTS, AMPLITUDE_IDENTIFY, and AMPLITUDE_UPDATE_COHORT_MEMBERSHIP. These are legitimate but production-impacting write actions.
Capability review items (1)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Low
SKILL.md:21
Hardcoded URL
**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API k
The skill directs users to configure the external Rube MCP endpoint. This is expected for the integration but creates third-party network and data-handling exposure.

Risk Factors

⚙️ External commands (50)
SKILL.md:16 SKILL.md:17 SKILL.md:21 SKILL.md:24 SKILL.md:25 SKILL.md:36 SKILL.md:39 SKILL.md:40 SKILL.md:41 SKILL.md:42 SKILL.md:43 SKILL.md:44 SKILL.md:45 SKILL.md:48 SKILL.md:49 SKILL.md:50 SKILL.md:59 SKILL.md:60 SKILL.md:63 SKILL.md:64 SKILL.md:65 SKILL.md:68 SKILL.md:71 SKILL.md:78 SKILL.md:79 SKILL.md:83 SKILL.md:85 SKILL.md:86 SKILL.md:87 SKILL.md:91 SKILL.md:92 SKILL.md:93 SKILL.md:101 SKILL.md:102 SKILL.md:103 SKILL.md:104 SKILL.md:108 SKILL.md:110 SKILL.md:111 SKILL.md:112 SKILL.md:117 SKILL.md:126 SKILL.md:141-145 SKILL.md:145-148 SKILL.md:148-152 SKILL.md:152-157 SKILL.md:157-158 SKILL.md:158-159 SKILL.md:159-160 SKILL.md:160-161
🌐 Network access (1)
SKILL.md:21
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-amplitude-automation/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-amplitude-automation/security.svg)](https://skillstore.io/skills/sickn33-amplitude-automation?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-amplitude-automation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-amplitude-automation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-amplitude-automation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). amplitude-automation security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-amplitude-automation/audits/7

BibTeX citation

@techreport{sickn33-sickn33-amplitude-automation-2026, author = {sickn33}, title = {amplitude-automation security audit report (audit version 7)}, institution = {Skillstore}, year = {2026}, number = {7}, url = {https://skillstore.io/skills/sickn33-amplitude-automation/audits/7}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "amplitude-automation security audit report (audit version 7)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-09" url: "https://skillstore.io/skills/sickn33-amplitude-automation/audits/7" identifiers: - type: other value: "skillstore:sickn33-amplitude-automation:audit:7" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
68
Community
91
Spec Compliance

What You Can Build

Investigate User Activity

Find an Amplitude user, resolve the internal ID, and review recent event activity with pagination guidance.

Maintain Product Cohorts

List cohorts, inspect details, update membership, and monitor async update status.

Instrument Analytics Events

Prepare event payloads, check timestamp format, and send events through the Amplitude MCP tools.

Try These Prompts

Check Amplitude Setup 
Search the Rube tools for current Amplitude schemas. Check whether my Amplitude connection is active before suggesting any workflow.
Find User Activity 
Find the Amplitude user for this application user ID, resolve the internal ID, and summarize recent activity with pagination notes.
Prepare Event Tracking 
Review the current send events schema, validate these event details, and ask for approval before sending them to Amplitude.
Update Cohort Membership 
List matching cohorts, confirm the target cohort ID, plan membership changes in batches, then track the async status after approval.

Best Practices

  • Search Rube tools before each workflow to use current schemas.
  • Confirm the Amplitude project, cohort, and user identifiers before mutating data.
  • Use status checks for async cohort updates and document the final result.

Avoid

  • Do not assume application user IDs are Amplitude internal IDs.
  • Do not send production events without explicit user approval.
  • Do not ignore pagination, rate limits, or eventual consistency delays.

Frequently Asked Questions

Does this skill require an Amplitude API key?
It requires an active Amplitude connection through Rube MCP. Authentication is handled through that connection.
Can it send new events to Amplitude?
Yes. It guides the AMPLITUDE_SEND_EVENTS workflow after checking the current tool schema.
Can it read user activity?
Yes. It finds the user first, then uses the internal Amplitude user ID for activity lookup.
Can it update cohort membership?
Yes. It can guide cohort membership updates and status checks for asynchronous operations.
Why does it search tools first?
Rube MCP schemas can change. Searching first reduces parameter mistakes and stale assumptions.
Is it safe for production analytics?
Use caution. Sending events and updating cohorts can change production analytics and targeting behavior.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/amplitude-automation

Ref

3e4b6c31a74a3bd1a291c98cf585d720cb9fbc88

Maintenance freshness

7/18/2026

Usage

6 downloads · 92 views

File structure

📄 SKILL.md