Operations · Intermediate

Verified

Automated verification

  • Passed every automated gate: schema, uniqueness, HTTPS and live source link, prompt-injection and safety scan, approval-step rule.
  • Drafted by deepseek-flash via DeepSeek API.
  • Second-model review: kimi-code/k3.1-pro (no critical or high findings).
  • Verified .
  • Automated checks and AI review only, not human review.
How verification works

Triage robot runtime recordings before review

Review recorded runs and flag divergence for human approval

Use with BotBento

Opens BotBento with this bot ready to create. You check it, create it in one click, then connect its apps. Nothing runs until you do.

  1. When something happensNew runtime recording
  2. ThenInspect trace and logs
  3. ResultDraft triage note

A bot watches for newly recorded robot runtime sessions and inspects logs and message traces. It prepares a concise triage note that highlights the first point of divergence, likely cause, and next checks. It leaves raw recordings untouched and queues any notification or status update for a person to approve.

Quick answers

What does it do?

Review recorded runs and flag divergence for human approval. Result: Draft triage note.

What does it need?

Tools: Terminal, Notes, Chat. Intermediate: some setup. The prompt includes an approval step.

How do I run it?

When something happens: New runtime recording. Copy the prompt below into a bot in BotBento.

Prompt to start with

BotBentoRecommended
When a new runtime recording appears, open its logs and message trace. Compare the recorded execution path with the expected schedule, note the first divergent topic or frame, and summarize likely causes and next checks. Do not alter, delete, or overwrite original recordings. Draft the triage note and any chat update, but wait for the user's approval before sending, posting, or filing it. If the trace is incomplete, ask for the missing files.