ptp-telemetry-status

Reports telemetry receiver status, store location, and per-epic run counts read-only.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-telemetry-status-almogmaayan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ptp-telemetry-status
Source: https://github.com/AlmogMaayan/ptp/tree/main/skills/ptp-telemetry-status
Command: npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-telemetry-status-almogmaayan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It answers whether the local ptp telemetry receiver is running, where its store lives, and how many runs are closed or unclosed per epic, without ever creating files or mutating state. ## Core Features & Use Cases - Read-only status report: Resolves telemetry mode and root from configuration independently of whether a store exists, and never creates directories or files. - Per-epic run accounting: Reports total, closed, and unclosed run counts per epic directory, plus the _unattributed/ bucket as its own health signal. - Three unambiguous states: Distinguishes mode off, mode on with no store, and mode on with unclosed runs, so an absent store is never misread as telemetry being off. - Use Case: After a pipeline run, ask for the telemetry status to confirm the receiver is up and check whether any run was left unclosed before starting the next change. ## Quick Start Ask the assistant to run the ptp telemetry status report and show the resolved mode, store root, and per-epic run counts.

Frequently Asked Questions about ptp-telemetry-status

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

FAQPage Schema
How do I check if the ptp telemetry receiver is running?▼

Run the telemetry status report, which probes the receiver using its identity and health wire contract and reports the environment, receiver, and lockfile state. It is strictly read-only and creates nothing.

How do I see closed and unclosed telemetry runs per epic?▼

The status report lists each epic directory with total, closed, and unclosed run counts, counting each run_id once. A run with any close line is closed; an open line with no close line is unclosed.

Does a missing telemetry store mean telemetry is turned off?▼

No. The mode is resolved from configuration independently of the store, so an absent store never implies mode off. A store can legitimately be absent when nothing has run yet.

What is the difference between /ptp:telemetry-status and /ptp:status?▼

The telemetry status command reports on the telemetry store and receiver, while /ptp:status is an unrelated OpenSpec command about the change lifecycle. They share a word but must never be routed to each other.

Can the telemetry status command modify or repair the store?▼

No. It creates no directory or file and runs no git command, branch guard, or openspec validation. Lockfile repair is owned by the receiver lifecycle, not the read-only report.