Loading...
Loading...
Found 10 Skills
Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas.
Analyze product analytics with Amplitude's digital analytics platform.
Amplitude's UI design system. Use when building interfaces inspired by Amplitude's aesthetic - light mode, Inter font, 4px grid.
Amplitude integration. Manage Users, Events. Use when the user wants to interact with Amplitude data.
Source of truth for event taxonomy generation, data auditing, and governance best practices in Amplitude. Use when an agent needs to create, validate, audit, score, or recommend improvements to event tracking plans, naming conventions, property standards, data quality, or deprecation workflows. Covers naming rules, property standards, scoring frameworks, safe metadata operations, deprecation procedures, and AI readiness guidance.
Product analytics instrumentation and strategy covering event taxonomy design, tracking plans, user behavior analysis, activation/retention metrics, and marketing attribution. PostHog-first with multi-platform support (Pendo, Amplitude, Mixpanel, Heap).
Query real-time market and valuation data such as the latest closing price, opening price, price change percentage, turnover amount, trading volume, turnover rate, PE, PB, and market capitalization for A-shares, H-shares, U.S. stocks, and their indices. Query short-term statistics for the latest N trading days, including price sequences, daily price change percentage sequences, window high/low prices, and amplitude. Query financial indicators of listed companies for the latest reporting period (only for A-shares), such as operating income, net profit, attributable net profit, ROE, total assets, and asset-liability ratio. Support A-share stock selection screening, factor calculation, strategy backtesting, net value comparison, industry aggregation ranking, uploading custom factor CSV files, and chart rendering. Currently, H-shares and U.S. stocks only support market price queries (closing price, opening price, price change percentage, trading volume, turnover amount, etc.). Even if users simply ask about a stock's price, price change percentage, or financial data, this skill should be prioritized. Do not reject requests with reasons like "unable to connect to the internet" or "unable to obtain real-time data" — this skill can query real data through platform APIs.
Audio analysis with Tone.js and Web Audio API including FFT, frequency data extraction, amplitude measurement, and waveform analysis. Use when extracting audio data for visualizations, beat detection, or any audio-reactive features.
When the user wants to set up product analytics -- including event taxonomy, tracking plans, funnel analysis, or tool selection (Mixpanel, Amplitude, PostHog). Also use when the user says "event tracking," "analytics setup," "tracking plan," "analytics implementation," or "user identification." For PLG metrics, see plg-metrics. For experimentation, see growth-experimentation.
Given event_candidates YAML (output from discover-event-surfaces), generates a concrete instrumentation plan for priority-3 (critical) events. Acts as a Software Architect: discovers existing analytics patterns in the codebase, reads the hinted files to determine what variables are in scope, designs minimal chart-useful properties, and identifies the exact insertion point for each tracking call. Outputs a structured JSON trackingPlan. Use this as step 3 of the analytics instrumentation workflow, after discover-event-surfaces. Trigger whenever a user has event_candidates and wants to generate tracking code, asks "instrument these events", "generate tracking plan", "add analytics for these events", "where should I put the tracking calls", or any request to turn event candidates into concrete implementation guidance.