ce-product-pulse

Generate time-window pulse reports summarizing usage, performance, errors, and follow-ups.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/xotong/claude-marketplace --skill ce-product-pulse-xotong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-product-pulse
Source: https://github.com/xotong/claude-marketplace/tree/main/plugins/compound-engineering/skills/ce-product-pulse
Command: npx skills add https://github.com/xotong/claude-marketplace --skill ce-product-pulse-xotong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates product usage signals, quality signals, and system performance data into a single, concise pulse report that helps teams detect drift, prioritize follow-ups, and communicate status quickly.

Core Features & Use Cases

  • Single-page pulse including usage, value realization, completions, and system performance.
  • Supports configurable lookback windows and automatic report saving to docs/pulse-reports.
  • Use cases include weekly health checks, launch-day checks, and post-mortem follow-ups.

Quick Start

Define your pulse configuration in .compound-engineering/config.local.yaml, then run Phase 1 to seed and Phase 2 to produce the first report.

Frequently Asked Questions about ce-product-pulse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a time-window product pulse report for usage and performance data?

A product pulse report summarizes usage, performance, errors, and follow-ups into a single-page, decision-ready summary that helps teams detect drift, prioritize actions, and communicate status quickly.

How do I configure the lookback window for an automated product health check?

Configuring the lookback window requires setting pulse_* keys inside the .compound-engineering/config.local.yaml block, which enables customizable time-window analytics for weekly health checks, launch-day checks, and post-mortem follow-ups.

Does the pulse report workflow require write access to my data sources?

No, the pulse report workflow operates with read-only data access, safely orchestrating analytics and tracing data to generate summaries without modifying your underlying product data sources.

What is the best way to consolidate product completions and system performance into a single summary?

The best way is to use an automated pulse report that orchestrates tracing and analytics to produce a single-page summary covering usage, value realization, completions, and system performance.

What are the limitations of using a single-page pulse report for post-mortem follow-ups?

The single-page format is designed for quick detection and communication, so it may lack the granular, deep-dive tracing details needed for complex post-mortem root cause analysis without querying optional data sources.