Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas.
70
60%
Does it follow best practices?
Impact
83%
1.23xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/amplitude-automation/SKILL.mdEvent ingestion: timestamp format, batching, and type validation
RUBE_SEARCH_TOOLS first
0%
100%
RUBE_MANAGE_CONNECTIONS setup
0%
100%
Connection ACTIVE check
0%
62%
Millisecond timestamp conversion
100%
100%
event_type included
100%
100%
user_id included per event
100%
100%
Batch events in single call
100%
100%
Event category validation
0%
0%
event_properties populated
100%
100%
Response parsed under data key
0%
0%
Workflow plan file produced
100%
100%
User ID resolution and activity retrieval workflow
RUBE_SEARCH_TOOLS first
0%
0%
RUBE_MANAGE_CONNECTIONS setup
0%
0%
FIND_USER called first
66%
100%
Internal ID used for activity lookup
86%
100%
FIND_USER search term
100%
100%
Limit parameter set to 100
100%
100%
Pagination awareness
37%
100%
Reverse chronological order noted
100%
100%
Response under data key
50%
100%
Runbook file produced
100%
100%
App user_id vs internal ID distinction
100%
100%
Cohort membership update: async pattern and ID resolution
RUBE_SEARCH_TOOLS first
0%
0%
RUBE_MANAGE_CONNECTIONS setup
0%
66%
LIST_COHORTS called first
100%
100%
Cohort ID extracted by name
100%
100%
Archived cohorts filtered
0%
0%
Users chunked into batches
50%
100%
Async update acknowledged
100%
100%
CHECK_COHORT_STATUS polling
100%
100%
request_id used for status check
100%
100%
Behavioral cohort limitation noted
100%
100%
Notes file produced
100%
100%
7cc63f3
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.