What problem does it solve? Stopping a local telemetry receiver safely is harder than it looks: process ids get reused, lockfiles go stale, and a listener on a port may belong to a different store. This Skill defines a strict verify-before-signal methodology so the ptp telemetry receiver is terminated only when identity is fully confirmed, and its lockfile is removed only after the receiver is confirmed down. ## Core Features & Use Cases - Five-conjunct verification: Confirms the recorded pid is live, the probe answered, the launch token matches, the reported pid equals the recorded pid, and the store identity matches before signalling anything. - Ordered stop semantics: Reads the lockfile, probes the recorded port, reloads the lockfile after the probe, signals the process, and removes the lockfile only after the port is confirmed unserved. - Structured outcome vocabulary: Reports one JSON object per invocation with outcomes such as stopped, already-stopped, stale-lockfile, mismatched-lockfile, not-stopped, and refused. - Use Case: A developer finished a coding session and wants to shut down the local telemetry receiver without risking killing an unrelated process that reused the pid, or deleting the only record of a receiver that is still running. ## Quick Start Ask the agent to stop the ptp telemetry receiver for this repository using the ptp-telemetry-stop skill and report the JSON outcome.
