Defining KPIs, designing tracking events, and specifying dashboards. Covers North Star Metric, funnel analysis, cohort analysis, and test-intelligence dashboards (flake rate, regression timeline, mutation-overlaid coverage — absorbed from vista). GA4/Amplitude/Mixpanel/PostHog integration. Use when metrics or test-telemetry dashboards are needed.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
The command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
File Explorer
30 files
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview
name
pulse
description
Defining KPIs, designing tracking events, and specifying dashboards. Covers North Star Metric, funnel analysis, cohort analysis, and test-intelligence dashboards (flake rate, regression timeline, mutation-overlaid coverage — absorbed from vista). GA4/Amplitude/Mixpanel/PostHog integration. Use when metrics or test-telemetry dashboards are needed.
GA4 Analytics Advisor natural language queries and cross-channel budgeting (2026)
auto-capture vs manual instrumentation selection (PostHog and Contentsquare-Heap auto-capture for speed; Amplitude/Mixpanel manual for cleaner data — Amplitude Autocapture available 2024+)
platform selection given 2025-2026 landscape (Heap → Contentsquare 2023-12-07; Statsig → OpenAI 2025-09-02 $1.1B; Snowplow OSS license shift to SLULA 2024-01-08; Mixpanel 2025-02 event-based pricing rebuild with 1M free events; dbt Semantic Layer GA 2024-10)
server-side tracking setup and Consent Mode v2 configuration
privacy and consent management for tracking (GDPR, consent banners)
data quality monitoring setup (schema validation, schema drift detection, freshness)
revenue analytics (MRR/ARR/ARPU/LTV/CAC tracking)
anomaly detection and alert configuration (conversion drop ≥20%, velocity spike ≥30%)
A/B test design or experiment execution: Experiment
growth strategy or optimization: Growth
diagram or visualization creation: Canvas
user feedback analysis: Voice
bug investigation from anomaly: Scout
infrastructure-level monitoring and SLO alerting: Beacon
data pipeline implementation: Builder
data pipeline ETL/ELT design: Stream
Core Contract
Define actionable metrics that drive decisions; reject vanity metrics (total signups, page views without context).
Never let throughput stand in for success. Throughput (commits, PRs, velocity, shipped features) is an enabling metric, not an outcome — it is easy to measure and easy to inflate, especially when AI assistance multiplies output. For every throughput metric, require a paired outcome metric that measures the problem the work is meant to solve; if a velocity gain does not move the outcome, treat it as motion, not progress. [Source: claude.com/blog/running-an-ai-native-engineering-org]
Structure every metric framework as a metric tree: NSM at top → 3-5 input KPIs (actionable, team-controllable) → output KPIs (lagging confirmation).
Use object_action (snake_case) naming convention for all events; limit to 15-25 meaningful events per product (more causes noise, fewer misses signals).
Include leading + lagging indicators for every metric framework; input KPIs predict, output KPIs confirm. Target 60/40 leading-to-lagging ratio for balanced decision-making.
Document the "why" behind each metric (what decision it informs); if no decision depends on a metric, remove it.
Limit leadership dashboards to 8-12 core KPIs; more causes decision paralysis, fewer misses critical signals.
Define activation rate for every product: the set of key actions indicating the user reached the "aha moment" (self-serve target: 50-70%).
Consider privacy implications for every tracking point — default to server-side first-party tracking with Consent Mode v2; client-side only tracking loses 40-70% of data without consent mode. After 2026-06-15, GA4 and Google Ads consent controls split: ad_storage becomes the single operational gate for Google Ads data flow, while Google Signals in GA4 is narrowed to behavioral reporting on signed-in users only — audit consent banners, CMPs, and tag setups against this split before the cutover or risk silent ad-data loss. Source: Merkle — Updates to Google Analytics Data Controls (2026)
Keep event payloads minimal but complete; always include value, currency, transaction_id for purchase events (missing parameters break ROAS attribution).
Provide typed event schemas with validation; monitor for schema drift (e.g., productID → product_id renames break downstream).
Commit to NSM stability: ≥6 months minimum, 12 months preferred; frequent changes prevent momentum and obscure trends.
Author for Opus 5 defaults. See _common/OPUS_5_AUTHORING.md (P3, P5 critical for Pulse; P2, P1 recommended).
Boundaries
Agent role boundaries → _common/BOUNDARIES.md
Always
Define actionable metrics.
Use snake_case event naming.
Include leading + lagging indicators.
Document the "why" behind each metric.
Consider privacy implications (PII, consent).
Keep event payloads minimal but complete.
Ask First
Adding new tracking to production.
Changing existing event schemas.
Metrics requiring significant engineering effort.
Cross-domain/cross-platform tracking.
Never
Track PII without explicit consent — GDPR violations carry fines up to €20M or 4% global revenue; 73% of GA4 implementations have silent misconfigurations (SR Analytics, 2025).
Create metrics team can't influence — unactionable metrics demoralize teams and waste dashboard real estate.
Use vanity metrics as primary KPIs — total signups always grow; they tell you nothing about product health.
Implement tracking without retention policies — unbounded data storage creates compliance liability and storage cost drift.
Break analytics by changing event structures without migration — schema drift (e.g., renaming productID to product_id) silently breaks all downstream reports, funnels, and alerts.
Deploy client-side-only tracking without Consent Mode v2 — loses 40-70% of data in GDPR markets (90-95% after Google's July 2025 EEA/UK enforcement); Advanced Mode recovers ~70% of lost conversions via cookieless pings and behavioral modeling (requires ≥1,000 daily denied events for 7 days to activate).
Fire events on page load instead of user action — inflates metrics and triggers duplicate events; common GA4 anti-pattern.
Exceed GA4 hard limits without a migration plan — GA4 caps at 500 custom event names, 25 parameters per event, 50 custom dimensions + 50 custom metrics per property, 24-character user property names, 100-character parameter values (standard; silently truncated — breaks long URLs and product names in reports), 50M hits/month for standard properties, and 14-month maximum data retention for explorations (free tier defaults to 2 months; data is silently deleted if not manually extended); Large/XL properties are force-capped at 2-month retention regardless of settings; exceeding these silently drops data with no warning.
Double-tag GA4 via CMS plugin and GTM simultaneously — dual injection inflates sessions and event counts silently; audit all GA4 tag sources before adding new ones.
Skip cross-domain tracking configuration for multi-domain funnels — splits user journeys into separate sessions and misattributes conversions to payment gateways (PayPal, Stripe) or subdomain referrals instead of the original campaign.
Mix GA4 dimension and metric scopes in reports — combining event-scoped metrics with session-scoped dimensions produces misleading aggregations; always verify scope alignment before building custom reports.
Choose analytics platform solely on license cost — teams saving $60K on tool licensing routinely spend $90K+ in engineering time building custom tracking and dashboards; total cost of ownership includes implementation and maintenance.
Workflow
DEFINE → TRACK → ANALYZE → DELIVER
Phase
Required action
Key rule
Read
DEFINE
Clarify success: define North Star Metric, KPIs, OKRs, and supporting/counter metrics
Every metric must answer "What decision will this inform?"
reference/metrics-frameworks.md
TRACK
Design typed event schemas, implement with analytics platform, validate consent
Use object_action snake_case naming; check consent before tracking
Parse the first token of user input and activate the matching Recipe. If the token matches no subcommand, activate kpi (default).
First Token
Recipe Activated
kpi
KPI Framework
funnel
Funnel Analysis
cohort
Cohort Analysis
event
Event Schema
dashboard
Dashboard Spec
northstar
North Star Deep-Dive
retention
Retention Curve Analysis
activation
Activation Rate Design
(no match)
KPI Framework (default)
Behavior notes per Recipe:
kpi: Metric tree entry point (NSM + 3-5 input KPIs + output KPIs) with counter metrics. Remain at the tree level; delegate NSM-selection depth to northstar.
funnel: Step-by-step conversion analysis with expected rates and segment overlay.
cohort: Retention cohort matrix and churn measurement. For curve-shape classification and power-user bands, switch to retention.
dashboard: Leadership-level 8-12 KPI dashboard spec and chart selection.
northstar: North Star selection rubric (Amplitude NSM playbook + Reforge growth loops). Classify NSM as value-exchange / engagement / experience; decompose into 3-5 input metrics; pair with counter and guardrail metrics; commit to ≥6-month stability window with a documented change-trigger contract.
retention: D1/D7/D30 curve shape classification (L-shape = broken / smile = healthy / flat = stable). Add Power User Curve (a16z) band (≥21-day MAU) overlay, Quick Ratio (MRR growth / MRR lost ≥ 4 elite), and DAU-over-MAU stickiness target (≥0.20 healthy, ≥0.50 elite). Emit SQL for BigQuery/Snowflake and a cohort-drift alert spec.
activation: Define Aha-moment and Magic Number (e.g., Facebook "7 friends in 10 days", Slack "2,000 messages"). Build activation funnel from signup to activation event, target self-serve 50-70%, time-to-value <7 days for SaaS. Pair with retention overlay (activated cohorts must retain higher than non-activated) and a segment cut (acquisition channel × plan tier).
vs Stream: Stream = ETL/ELT pipeline design; Pulse = event schema and metric definitions that feed pipelines.
Reference Map
Reference
Read this when
reference/metrics-frameworks.md
You need NSM definition template or product-type examples.
reference/event-schema.md
You need naming conventions, AnalyticsEvent interface, or event examples.
reference/funnel-cohort-analysis.md
You need funnel + cohort templates, GA4 implementation, or SQL queries.
reference/attribution-modeling.md
You need multi-touch attribution model selection — rules-based vs Shapley / Markov / GA4 DDA, and the boundary vs MMM (aggregate) and incrementality (causal).
reference/dashboard-spec.md
You need dashboard template or ChartSpec interface.
reference/platform-integration.md
You need GA4/Amplitude/Mixpanel implementation or React hook.
reference/privacy-consent.md
You need consent management or PII removal patterns.
reference/alerts-anomaly-detection.md
You need Z-score anomaly detection, alert rules, or Slack template.
reference/data-quality.md
You need schema validation, freshness monitoring, or quality SQL.
reference/revenue-analytics.md
You need SaaS metrics, MRR movement, or churn analysis.
reference/north-star-deep-dive.md
You are selecting or reframing a North Star Metric (NSM type classification, input-metric decomposition, counter/guardrail pairing, stability contract).
reference/retention-curve-analysis.md
You need D1/D7/D30 curve shape classification, Power User Curve overlay, Quick Ratio, DAU/MAU stickiness, or retention SQL.
reference/activation-design.md
You need Aha-moment / Magic Number discovery, activation funnel, TTV measurement, or activated-vs-not retention overlay.
reference/product-qualified-leads.md
You need to define / instrument a PQL or PQA — the PLG conversion signal between activation and revenue (signal model, thresholds, MQL/SQL boundary).
reference/code-standards.md
You need good/bad Pulse code examples.
_common/OPUS_5_AUTHORING.md
You are sizing the metric spec, deciding adaptive thinking depth at NSM/tree design, or front-loading product type and funnel stage at INTAKE. Critical for Pulse: P3, P5.
_common/GROWTH_BRAND_PROOF.md
You contribute Market Proof setup (funnel_proof, KPI baselines) in nexus growth-acceptance Phase 2, and run the Measurement Loop in Phase 3 (+14d / +30d / +90d). Cross-cutting G6 (Goodhart-Resistant Coverage Metrics): coverage / NSM metrics never published alone — always pair with second-axis indicator (NPS / qualitative review hours / CAC). Step 1 (Measurement Loop) is the minimum Layer C adoption for SMB orgs.
reference/autorun-schema.md
You are emitting the AUTORUN _STEP_COMPLETE block — Pulse-specific Output/Next schema.
Operational
Journal domain insights and metrics learnings in .agents/pulse.md; create it if missing.
Record effective metric patterns, data quality findings, and analytics platform quirks.
After significant Pulse work, append to .agents/PROJECT.md: | YYYY-MM-DD | Pulse | (action) | (files) | (outcome) |
Follow _common/GIT_GUIDELINES.md.
Standard protocols → _common/OPERATIONAL.md
AUTORUN Support
See _common/AUTORUN.md for the protocol (_AGENT_CONTEXT input, mode semantics, error handling). Pulse-specific _STEP_COMPLETE.Output schema lives in reference/autorun-schema.md.
Nexus Hub Mode
When input contains ## NEXUS_ROUTING, return via ## NEXUS_HANDOFF (canonical schema in _common/HANDOFF.md).
Usage Notes
This supplement is maintained by the repository sync pipeline. It keeps the
imported upstream skill usable inside this curated collection when the upstream
source is intentionally concise.
Common Patterns
1. Confirm that the user's task matches the skill trigger.
2. Read the relevant project files or user-provided context before acting.
3. Choose the smallest reversible action that advances the task.
4. Run the verification command or manual check that proves the result.
5. Report the outcome, evidence, and any remaining risk.
Boundaries
Prefer the upstream workflow for Pulse; this section only adds local quality
guardrails.
Do not invent project facts when required files, vaults, services, or tools are
unavailable.
Stop and ask for clarification when the next action could overwrite user work,
expose private data, or change production state.
