Product Pulse

product-pulse queries the product's data sources for a given time window and produces a compact, single-page report covering usage, performance, errors, and followups. Each report is stored as a GitHub issue labeled tunan:pulse and the key points are surfaced in chat. The list of tunan:pulse issues is the browseable timeline of past pulses.

The skill does not mutate the product, the database, or any external system. Its only writes are pulse settings merged into the repo's tunan:config issue body and the report itself, both written to GitHub as issues (markdown body, no local file). MCP and other data-source tools are invoked read-only; if a tool offers write modes, do not use them.

Interaction Method

Default to the platform's blocking question tool: AskUserQuestion in Claude Code (call ToolSearch with select:AskUserQuestion first if its schema isn't loaded), request_user_input in Codex, ask_user in Gemini, ask_user in Pi (requires the pi-ask-user extension). Fall back to numbered options in chat only when no blocking tool exists in the harness or the call errors (e.g., Codex edit modes) — not because a schema load is required. Never silently skip the question.

Ask one question at a time. Reserve multi-select for first-run configuration only.

Lookback Window

The lookback window is the time range this skill was invoked with (e.g. 24h, 7d) — present in the current prompt or conversation, whether the user gave it directly or a calling skill passed it.

Interpret the argument as a time window. Common forms: