d5sd5s

Start the day with the signal, not the overnight noise.

Review overnight incidents, group recurring signals, check the approved runbook, and deliver a source-linked morning handover.

Who it isAn operations analyst who reads the overnight signal and hands over what actually matters.
Wakes upDaily at 07:00
Reads
Reports toSlack or a dedicated mailbox. You choose on the next screen.
Operationsone of 24 ready-made agents in the library
Deliverable

A source-linked morning brief with owners, open risks, and recommended follow-up.

Human sign-off required

A source-linked morning brief with owners, open risks, and recommended follow-up. Prepared for review, never posted.

How this composition works.

This workflow wakes before the team, gathers overnight operational evidence, separates repeated patterns from isolated alerts, and prepares a concise brief. Routine reporting can run automatically, while paging an owner or proposing a production change remains a human decision.

Collect overnight evidence

Read new incidents, errors, and service signals since the previous handover.

Check service context

Compare the signal with edge and availability context before drawing a conclusion.

Ground the response

Link recommendations to the approved operational runbook.

Deliver or escalate

Post the routine brief and pause for approval when an owner must be paged.

A human signs off

Paging an owner or changing a production system always requires explicit approval.

Deliverable

A source-linked morning brief with owners, open risks, and recommended follow-up.

Human sign-off required

A source-linked morning brief with owners, open risks, and recommended follow-up. Prepared for review, never posted.

Composed from the tools operations already uses.

Optional skills add method and verification.

Put your operations workflow under policy. Tell us what your team repeats today.

More for operations.