Product and business analytics router: event instrumentation, KPIs, A/B tests, cohorts, funnels, real-time pipelines, and data visualization. Topics: ab-testing, analytics-events, cohort-analysis, data-visualization, funnel-analytics, kpi-framework, metrics-instrumentation, real-time-analytics.
Router skill. Resolve topic, then Read EXACTLY ONE playbook from routes:.
Never preload the cluster — one topic in, one playbook out. [CONFIG]
A request touches product/business measurement: defining metrics, instrumenting or auditing events, designing or reading an experiment, building cohorts/funnels, or charting results. Not for app feature code, infra, or generic data-engineering ETL — route those to their own clusters. [INFERENCIA]
topic (required; infer from request, ask only if two routes fit),
depth (quick=essentials, deep=full playbook with per-step verification).[DOC] [CONFIG] [CÓDIGO] [INFERENCIA] [SUPUESTO])
on every non-obvious claim. [DOC]analytics-events; wiring SDK/server emit → metrics-instrumentation.ab-testing; "where do users drop?" → funnel-analytics.cohort-analysis; live dashboards/streaming → real-time-analytics.kpi-framework; rendering a chart/figure → data-visualization.Discover → Analyze → Execute → Validate. Gates: constitution v6.0.0, evidence tags, script-first. [CONFIG]
[SUPUESTO] paired with a
verification step. [DOC]Routing guard and gate live in assets/ — assets/routing-checklist.md
(resolve one topic) and assets/quality-rubric.json (guardian gate). [CONFIG]
Loading multiple playbooks; guessing a topic instead of asking when two fit; reporting metrics without instrumentation provenance; calling a test before it reaches significance; inventing benchmark numbers. [SUPUESTO]
fdad39c
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.