gossipper-analyzelisted

# gossipper-analyze — Output Interpretation Interpret Gossipper outputs and produce structured findings. Pinned to **Gossipper 0.1.60-rtcpmuxpatch2** (sipcapture/gossipper on `main`, audited 2026-05-18). ## When to use this skill - Read a "Run report" from gossipper-run and start an analysis. - Classify failures from per-call records (`success: false` + `error` string) and summary counters; surface dominant failure cause. - Compute latency verdicts (`invite_rtt`, `call_length`, custom `rtd` timers). - Compute media-quality verdicts (RTCP loss, jitter, per-call RTP floor). - Convert RTCP jitter fields (`media.RTCPMaxJitter` / `RTCPMinJitter` / etc., in RTP timestamp units) to ms. - Decide whether a run passed health thresholds (or apply them post-hoc if `-health_*` wasn't set). - Propose threshold values for the next run, by intent. - Surface Call-IDs, time windows, `hep_capture_id`, `self_tag` for downstream HOMER/qryn correlation. - Interpret exit code 2 and what to do about it. ## When NOT to use this skill | Task | Owner | |---|---| | Invoke gossipper, pick flags, deploy | gossipper-run | | Write or modify scenario XML | gossipper-build | | Query HOMER/qryn ClickHouse directly | separate query layer (out of scope here) | | Decide whether to escalate findings to humans / autonomous controllers | caller of this skill | This skill reads files and produces verdicts. It does not run, write, or query. ## Inputs from gossipper-run After every run, gossipper-run surfaces a