This skill configures metric alerts and anomaly detection rules for analytics pipelines. Use when asked to set up threshold alerts, configure anomaly detection, or define escalation policies for KPI movements. Also consider when a new metric dashboard ships without alerting coverage. Suggest when a north star metric changes or a new instrumentation spec is approved without corresponding alerts.
This skill estimates analytics and data engineering effort for product initiatives. Use when asked to size instrumentation work, estimate dashboard build time, or scope a data pipeline. Also consider when sprint planning requires analytics capacity allocation. Suggest when a PRD is approved without a data workstream estimate.
This skill defines measurable analytics goals aligned to product and business objectives. Use when asked to set data team OKRs, define success metrics for an initiative, or translate business goals into queryable KPIs. Also consider when a quarterly planning cycle begins without analytics goals. Suggest when product goals lack quantitative success criteria.
This skill reviews instrumentation plans for clarity, completeness, and measurability. Use when asked to QA an instrumentation spec, review event naming conventions, or validate property coverage. Also consider when a new instrumentation spec is drafted. Suggest when implementation is about to begin on an unreviewed spec.
This skill plans the instrumentation implementation approach across client and server. Use when asked to create an instrumentation rollout plan, coordinate SDK integration, or sequence event deployment across platforms. Also consider when a new product surface launches without a data collection strategy. Suggest when an instrumentation spec is approved but no implementation plan exists.
This skill writes the instrumentation specification defining what events and properties to track. Use when asked to design an event taxonomy, define tracking properties, or create a measurement plan. Also consider when a new feature enters development without a tracking spec. Suggest when a PRD has success metrics but no corresponding event definitions.
This skill sizes the addressable market using quantitative data sources and modelling. Use when asked to estimate TAM/SAM/SOM, validate market opportunity, or quantify segment size. Also consider when a business case requires market size justification. Suggest when a new product idea lacks demand-side quantification.
This skill reviews whether the north star metric remains valid and actionable. Use when asked to audit the north star definition, assess metric health, or evaluate whether the north star still correlates with business outcomes. Also consider at quarterly planning boundaries. Suggest when the north star has not moved despite significant product changes.