ce-product-pulse

Invoke the skill with a lookback argument such as 24h, 7d, or 1h. It queries your configured analytics, tracing, and payments sources in parallel, then assembles a single-page report saved to docs/pulse-reports/ with headlines surfaced in chat.

The pulse supports product analytics tools like PostHog or Mixpanel, tracing tools like Sentry or Datadog, payments providers like Stripe, and an optional read-only database. Sources are configured during the first-run interview and stored as pulse_* keys in .compound-engineering/config.local.yaml.

No. The interview explicitly refuses read-write database credentials and only accepts read-only replicas or read-only users. Database access is entirely optional, and many products complete the pulse using analytics and tracing alone.

No. Saved reports never contain PII such as user emails, account IDs, or message content. Quality scoring captures only a count distribution and anonymized notes for sessions scored below 4.

Analytics and tracing tools have ingestion lag, so querying right up to the current moment under-reports recent events. The buffer shifts the window's upper bound back 15 minutes so the most recent data is accurate.

The pulse does not set thresholds, send alerts, or report what shipped; it presents numbers for the reader to interpret. It consolidates a single-page read and does not replace deep investigation in native analytics or tracing dashboards.