Cuiar
Sign inDownload

Draft status page updates during an incident

A clear update from the incident channel and your monitors, posted to your status page after you approve it.

  • You start it: When you start it
  • Asks you first
Use in CuiarRun from your AI agent

What it does

The task

Read the Slack channel incident channel from the start of the incident and the Datadog monitors that are in alert. Read the last update on status page url so that you do not repeat it. Write a status page update of at most 60 words: what users see, which features are affected, what we do now and the time of the next update. Use plain words, no internal names and no guesses about the cause. Ask me before you post it.

  • It works in Slack, Datadog and any status page, in the workspace you pick, and signs in with passwords from your Cuiar vault.
  • It runs once, when you start it.
  • It stops for your approval before it sends, posts, pays, books or changes a record.

What you give it

BlankWhat to giveExample
incident channelThe Slack channel of the incident#inc-export
status page urlYour public status pagehttps://status.brightleaf.app

What you get back

An example run with the example values above. Your run uses your own data.

Incident: CSV export failures, started 4 Nov 11:50

Datadog: export-worker error rate 38%, in alert since 11:52

Last public update: 12:05, "Investigating"

Draft update, status "Identified":

"Exports of invoices as CSV fail for some accounts. Other features work. We found the problem and are rolling out a fix. Next update by 13:30."

Waiting for your approval to post on status.brightleaf.app.

Run it in Cuiar

  1. 01

    Open it

    Click Use in Cuiar on this page. The side panel opens with the task in the composer.

  2. 02

    Fill in 2 blanks

    Type incident channel and status page url. Tab moves to the next blank.

  3. 03

    Run it

    Run sends it to the agent. Follow each step in the panel, and stop it at any time.

From the terminal

cuiar exec "Read the Slack channel #inc-export from the start of the incident and the Datadog monitors that are in alert. Read the last update on https://status.brightleaf.app so that you do not repeat it. Write a status page update of at most 60 words: what users see, which features are affected, what we do now and the time of the next update. Use plain words, no internal names and no guesses about the cause. Ask me before you post it."

Run it from your AI agent

Claude Code, Codex, Cursor and other MCP clients reach Cuiar at https://mcp.cuiar.com/mcp. Add the server one time, then ask for the task in plain words, or call run_task yourself.

1. Add Cuiar to Claude Code

claude mcp add --transport http cuiar https://mcp.cuiar.com/mcp

2. Ask your agent

Use the Cuiar tool run_task to run my "Draft status page updates during an incident" template with incident channel = #inc-export; status page url = https://status.brightleaf.app.

Setup for other agents: AI agents.

The tool call

{
  "name": "run_task",
  "arguments": {
    "task": "Read the Slack channel #inc-export from the start of the incident and the Datadog monitors that are in alert. Read the last update on https://status.brightleaf.app so that you do not repeat it. Write a status page update of at most 60 words: what users see, which features are affected, what we do now and the time of the next update. Use plain words, no internal names and no guesses about the cause. Ask me before you post it."
  }
}

Related templates

All engineering templates

  • Engineering

    Write an incident postmortem from the timeline

    A blameless draft with the timeline, impact, cause and actions, built from chat, monitors and deploys.

    You start it: When you start it
    • Slack
    • Datadog
    • GitHub
    • +1 more: Google Docs

  • SalesAsks first

    Find a customer reference for a deal

    The happy customers that best match a prospect, with proof, and a request to each account owner.

    You start it: When you start it
    • Salesforce
    • G2
    • Slack

  • OpsAsks first

    Set up accounts for a new employee

    Invites to each tool your team uses, with the same access as a colleague in the same role.

    You start it: When you start it
    • Any admin panel
    • Slack
    • Notion
    • +1 more: Google Docs

  • OpsAsks first

    Remove a former employee's access to your tools

    Every account the person still has, closed after your approval, with their files moved to a new owner.

    You start it: When you start it
    • Any admin panel
    • Google Drive
    • Slack
    • +1 more: GitHub

  • OpsAsks first

    Answer questions in a Slack channel

    An answer from your wiki in the thread, with the sources.

    On an event: When someone asks a question in the channel
    • Slack
    • Notion

  • Ops

    Catch up on busy Slack channels

    Decisions, questions for you and mentions from your channels, in a short morning brief.

    On a schedule: Every weekday at 8:30
    • Slack