on-call

DE//AGENT currently lists 2 resources under on-call: 1 plugin, 1 agent. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Learning objectives are not yet documented for these records — curation adds them evidence-first. What the entries cover today, from their own summaries:

• Runbook Runner
• Guide an on-call engineer through a data incident and produce the postmortem. Incident Assistant

These resources map to stage: Reliability (2). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

How scores are computed: source quality score.

Highest composite score first:

1. Runbook Runner score 35.6 — beginner
2. Incident Assistant score 30 — intermediate

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

Start here if you're new: Runbook Runner.

Security-flagged entries: Runbook Runner (1 flag), Incident Assistant (3 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

• Runbook Runner — Loads the production playbooks into the agent, matches an alert to a runbook, and walks the operator through diagnosis and mitigation step by step. details
• Incident Assistant — Guide an on-call engineer through a data incident and produce the postmortem. details

Real install commands from the registry — read the source before running any of them:

amp plugin add de-agent/runbook-runner

Runbook Runner — review first

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.