pi-events-doctor

Diagnoses pi-events-daemon health by checking a persistent risk register against SQLite and log evidence.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/peachest/skills --skill pi-events-doctor-peachest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pi-events-doctor
Source: https://github.com/peachest/skills/tree/main/in-progress/pi-events-doctor
Command: npx skills add https://github.com/peachest/skills --skill pi-events-doctor-peachest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Once the pi-events-daemon has been running in real usage, known risks (parked backlog, dead-letter growth, wake failures, low adoption) can silently degrade without any telemetry to surface them. This Skill carries a persistent risk register so discovered risks are never re-derived from scratch, and runs evidence-based periodic diagnostics on the daemon. ## Core Features & Use Cases - Risk Register Maintenance: Tracks 10+ known daemon risks (R1-R10) plus environmental migration risks in references/risks.md, updating status and dates after every diagnosis. - Evidence-Based Diagnosis: Runs read-only SQLite queries, journalctl log audits, and transcript sampling per references/checks.md, issuing verdicts of healthy, degraded, or triggered only with supporting evidence. - Remediation Routing: Applies immediate fixes where safe (FTS5 index rebuild, dead-letter cleanup) and escalates structural issues to the issue tracker with links recorded in the register. - Use Case: After the daemon has run for a few weeks, a user notices events are not being delivered. Invoke this Skill to check parked delivery ages, dead-letter reasons, and wake accepted-to-verified latency, then record findings back into the risk register. ## Quick Start Run a health diagnosis on the pi-events-daemon and update the risk register with verdicts for each known risk.

Frequently Asked Questions about pi-events-doctor

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

FAQPage Schema
How do I diagnose a pi-events-daemon that stopped delivering events?▼

Run the four-step diagnostic flow: collect evidence via read-only SQLite queries and journalctl logs, judge each risk in the register as healthy, degraded, or triggered, apply safe fixes like dead-letter cleanup, then write results back to references/risks.md.

What is a risk register and how does it help daemon maintenance?▼

A risk register is a persistent table of known risks with trigger signals, check methods, and mitigations. It ensures discovered risks are never re-derived from scratch, and each diagnosis updates statuses and dates so the register grows more complete over time.

How do I check for parked or dead-letter delivery backlog in SQLite?▼

Query the deliveries table grouped by state to get counts and age ranges, and group dead-letter rows by reason. Parked rows averaging older than 7 days signal permanent subscriber departure, while growing dead-letter counts need triage.

Can this Skill automatically fix daemon problems it finds?▼

No. The Skill is read-only during diagnosis and never executes checkers or side-effect operations. Safe fixes like FTS5 index rebuilds are listed separately and require user confirmation; structural problems are escalated as issues.

Why does the daemon have no real-time monitoring or alerts?▼

The daemon intentionally ships without telemetry, so all metrics come from after-the-fact batch queries of its persistence layer and logs. Real-time alerting is a post-MVP telemetry topic tracked separately, not something this Skill fabricates.