القائمة
Use when you need to write a Grafana annotation for a confirmed Autoschrute incident window after the mutation gate has been explicitly approved.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | autoschrute-add-annotation |
| description | Use when you need to write a Grafana annotation for a confirmed Autoschrute incident window after the mutation gate has been explicitly approved. |
| metadata | {"owner":"ocm","last_updated":"2026-03-05","harnesses":["cline","claudecode","opencode","codex"]} |
Run scripts/annotate.py to write a Grafana annotation to a dashboard/panel at the midpoint of an incident time range.
This is typically used by the Autoschrute workflow to mark an incident window on a Grafana panel for later debugging / correlation.
scripts/annotate.pyscripts/requirements.txtPython 3 available on PATH.
Dependencies installed (recommended via venv):
python3 -m venv .venv
source .venv/bin/activate
python3 -m pip install --upgrade pip
python3 -m pip install -r ./scripts/requirements.txt
By default, the script reads:
{env:HOME}/devops_token.envYou can override the location with the environment variable:
TOKEN_FILE=/path/to/fileThe first line of the token file must match:
OP_TOKEN="<your_token>"
If the token is invalid/expired (typically shows up as HTTP 401/403), stop and refresh your OP token (per your team’s standard process), then re-run.
All scripts are located in the skill's scripts directory.
All inputs are required flags to annotate.py:
--region (e.g. us-ashburn-1)--dashboardUid (Grafana dashboard UID)--panelId (Grafana panel ID on that dashboard)--startTimeInMs (incident start time, epoch milliseconds)--endTimeInMs (incident end time, epoch milliseconds)--text (annotation text to write)The script writes the annotation at:
middle_time = (startTimeInMs + endTimeInMs) // 2
python3 scripts/annotate.py \
--region <region> \
--dashboardUid <dashboard_uid> \
--panelId <panel_id> \
--startTimeInMs <epoch_ms> \
--endTimeInMs <epoch_ms> \
--text "<annotation text>"
If you need a non-default token file:
TOKEN_FILE=/path/to/devops_token.env \
python3 ./scripts/annotate.py \
--region <region> \
--dashboardUid <dashboard_uid> \
--panelId <panel_id> \
--startTimeInMs <epoch_ms> \
--endTimeInMs <epoch_ms> \
--text "<annotation text>"
TOKEN_FILE={env:HOME}/devops_token.env \
python3 scripts/annotate.py \
--region us-ashburn-1 \
--dashboardUid abcDEFgHiJk \
--panelId 12 \
--startTimeInMs 1762348800000 \
--endTimeInMs 1762352400000 \
--text "Autoschrute: annotated incident INC123456 (midpoint)"
Only consider the output of annotate.py itself when deciding whether this skill succeeded.
Ignore other terminal/agent noise (for example: unrelated ssh-add, keychain, shell prompts, etc.).
Pass criteria (from annotate.py stdout):
Reading token from file ...Annotating time <some_number>Success!!Failure criteria (from annotate.py stdout/stderr):
Error reading token file ...ERROR: failed to annotate grafana panel ...OP_TOKEN="...". Note that the quotes are required around the token value.ModuleNotFoundError): install dependencies from scripts/requirements.txt.Read, create, update, inspect, and reply to Bitbucket pull requests or commit diffs using Bitbucket URLs plus environment-backed auth. Use when Codex needs Bitbucket API operations for PR metadata, compare or commit evidence, PR discussion threads, PR creation/update, reviewer preservation, or prefixed replies. This skill does not perform full code-change review or own code remediation.
Review change-management tickets such as Jira CHANGE or CM requests for deployment readiness, scope drift, documentation quality, and runbook adherence. Use when Codex needs to assess implementation steps, validation evidence, rollback clarity, Shepherd release scope and plan diffs, regional outliers, manual data-fix or host-maintenance procedures, team-specific runbook alignment, and commit or artifact-version alignment, and optionally write findings back to the ticket.
Bootstrap a local Codex setup from this shared starter repo. Use when an engineer needs an interactive onboarding flow that asks for local paths, required MCP settings, and only the overrides that differ from the shared Enterprise ChatGPT defaults, then generates or repairs a real local Codex config and verifies that shared path placeholders were resolved.
Use when onboarding OCI users to available packs, registry entries, PromptLib spaces, ORA skills, Skills Hub / AI Skills Registry, Codex Enterprise apps/connectors, or non-pack content sources after installing OCI starter packs.
Inspect DevOps MFO or region-build flock dependency status for a specific region, project, flock, and phonebookId. Use when Codex needs to determine which region-build phases are satisfied, unsatisfied, or optional; identify whether a flock has published the required capabilities; recursively trace missing capability producers; discover related infrastructure or application flocks from the dependency graph; or explain which upstream project or flock is blocking publication.
Preflights local ossh and oci-ops access, reads a Jira ticket to identify a target hostname and region, validates OCI authentication, resolves the tenancy OCID, and returns the appropriate oci-ops SSH connection command. Use when a user asks to SSH to an OCI host from a Jira ticket, set up ossh or oci-ops access, resolve a host region or tenancy, or needs an oci-ops SSH command.