Skip to content
Spark.
AgentEngineeringOperations

Wake up to context, not a blank page

An alert wakes the on-call; instead of a blank page, an AI situation brief pulls what changed, whether it happened before, and the signals around it, each line traced to its source, with the diagnosis left to the human.

Updated

Before you start

What you need
The alert itself, plus somewhere to read recent deploys, past incidents and monitoring.
Connector (MCP)
Recommended. It reads your deploy and change records, earlier incidents and your monitoring, which is what the brief is assembled from.
Without a connector
Paste the alert and point it at the records yourself. It works, but at two in the morning that is the part you least want to be doing.

A connector, often called MCP, lets an assistant read your tools directly instead of you pasting. Set it up once, then it reads those tools on its own. How that is done differs per assistant, so check its own documentation.

How to try it

  1. Download the skill and unzip it, before you need it. Inside are the instruction, the brief template, and a page on loading it.
  2. If your assistant reads skills, copy the oncall-context folder into the place it reads them from. If it does not, use Copy as text instead: that is the same instruction with the template already inlined.
  3. Replay an alert you already handled and compare its brief with what you found that night.
  4. Check that every item names its source, that gaps read [unknown], and that it never states a cause.
  5. Keep it beside you on the next page. It assembles context, you diagnose.
Download skill

Download to install it once. Copy to paste it into a chat.