Safe assistant workflows

Start with capabilities so the assistant identifies the bound account and effective scopes. A natural-language request is not a guarantee that every required tool or permission exists.

Daily review

Read my account capabilities, list degraded and down checks, and summarize ongoing incidents. Do not change anything or retrieve heartbeat URLs.

The assistant can use capabilities, filtered check lists and incident reads. It should follow pagination rather than claiming the first page is the whole account.

Investigate response time

For this website check, compare seven-day recorded latency and incident-free uptime. Explain missing data separately from successful measurements.

Use metrics, runs, history and uptime. Probe-specific metrics require a source ID from the same check’s runs. Latency cannot prove availability; paused/pending history is not reconstructed.

Prepare a new check

Inspect my account limits and propose a heartbeat check for a daily backup with ten minutes of grace. Show the configuration before creating it.

Before writing, verify account, kind, expected interval and scopes. Reuse the same idempotency key on retries. Creating a heartbeat does not install it in the job; secret URL entry is a separate private action.

Organize a private dashboard

Create a private dashboard for these existing checks and attach them. Do not publish it or modify any existing public dashboard.

Create a private custom dashboard and attach owned checks. A returned public URL from another dashboard does not authorize sharing or membership changes. Reorder requires a full group list, not a partial favorite list.

Reached a quota

The assistant should state the operation did not complete, explain the returned limit and display the supplied upgrade URL if non-null. It should identify the named account and ask a billing-authorized member when needed. It must not invent a purchasing URL or initiate a subscription.

Protect credentials

Do not ask the assistant to paste heartbeat URLs or manual tokens into chat. Use local private input/configuration. Prefer a connection without checks:ping_urls for routine monitoring review.