Prepare an Incident Summary
Combine incident details and comments for a response handoff.
/oo Better Stack: Read Better Stack incident [incident ID] and its comments. Summarize the timeline, current state, and response notes present in the records.
Choose an incident or reporting window to prepare an incident summary and take a requested response action.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Combine incident details and comments for a response handoff.
/oo Better Stack: Read Better Stack incident [incident ID] and its comments. Summarize the timeline, current state, and response notes present in the records.
Acknowledge a specifically identified incident and report its returned state.
/oo Better Stack: Acknowledge Better Stack incident [incident ID] as [responder name]. Report the returned incident state.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect a Better Stack API key.
Connect Better Stack →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
This connection reads incident details and comments, creates incidents, acknowledges them, and supports escalation.
Read incidents and the discussion attached to them.
Create, acknowledge, or escalate incidents when requested.
List Better Stack incidents with optional date and status filters.
better_stack.list_incidents Get a Better Stack incident by ID with included resource context when available.
better_stack.get_incident Create a Better Stack incident and alert the current on-call responder.
better_stack.create_incident Acknowledge a Better Stack incident to stop further escalations.
better_stack.acknowledge_incident Escalate a Better Stack incident to a user, team, schedule, policy, or organization.
better_stack.escalate_incident List all comments attached to a Better Stack incident.
better_stack.list_incident_comments List Better Stack metadata records for incidents or other supported owner types.
better_stack.list_metadata No matching tools.
No. Acknowledgement stops escalation and records that someone is responding. It does not resolve the incident.
Yes. Read the incident comments alongside its details to include the returned discussion and response context.
Yes. Provide a summary and explicitly request creation, with the desired alert options or escalation policy where needed.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.