rootly

Rootly - Printing Press CLI

Prerequisites: Install the CLI

This skill drives the rootly-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install rootly --cli-only
   

2. Verify: rootly-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.4 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:

go install github.com/mvanhorn/printing-press-library/library/monitoring/rootly/cmd/rootly-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

The official rootly-cli exposes a handful of resource groups; Rootly's API has ~98. This CLI types the entire surface, then adds what no Rootly tool has: a local SQLite mirror powering offline incident-similarity (related), solution-mining (fixed-last-time), MTTR/MTTA analytics (mttr), service scorecards (service-health), and cross-schedule coverage-gap detection (coverage-gaps) - the same agentic capabilities the AI-Labs MCP server reaches a remote service to compute, here for free in your terminal.

When to Use This CLI

Reach for this CLI when you are operating Rootly from a terminal or an agent loop: declaring and updating incidents, checking who is on call across services, computing reliability analytics for a review, or gating a deploy on incident state. It is the right tool when you want offline, composable answers (pipe to jq, gate on exit codes) instead of clicking through the Rootly web UI, and especially when an MSP-style portfolio of many services makes per-service browsing impractical.

Anti-triggers

Do not use this CLI for:

• Do not use this CLI to drive the Rootly web UI (Slack-channel creation, Zoom bridges, status-page theming) - those are UI/integration workflows the API does not expose as commands.
• Do not use the 17 analytics commands (related, mttr, oncall-now, ...) before a sync - they read the local SQLite mirror and return empty results on a cold store.
• Do not use 'digest' for an end-of-shift summary scoped to one schedule; use 'handoff' instead.
• Do not use 'escalation-trace' for the portfolio-wide who-is-on-call view; use 'oncall-now' instead.
• Do not use 'sla-breach' for historical mean-time trends; use 'mttr' instead.

Unique Capabilities

These capabilities aren't available in any other tool for this API.

Incident intelligence (offline)

• related - Find the past incidents most similar to a given one, ranked, so you can see how this class of problem played out before.

  Reach for this during triage when a symptom feels familiar - it surfaces prior incidents and their resolutions without a remote ML round-trip.

  rootly-cli related INC-1234 --agent --limit 5
  

• war-room - One screen for an active incident: header, severity/status, full timeline, open action items, the on-call for the affected service, and the next escalation rung.

  Use at the top of an incident to get full situational context in one command instead of five browser tabs.

  rootly-cli war-room INC-1234 --agent
  

• fixed-last-time - Mine the resolution notes and action items from a service's past incidents to surface what actually resolved this class of problem.

  Pick this when an alert smells like a repeat - it answers 'what did we do last time' from history instead of guesswork.

  rootly-cli fixed-last-time <service-or-query> --agent --limit 10
  

• postmortem-skeleton - Emit a paste-ready post-mortem markdown skeleton for an incident: timeline, action items, severity, duration, and affected services.

  Use at the start of a retrospective to skip the copy-paste assembly and go straight to analysis.

  rootly-cli postmortem-skeleton INC-1234
  

• action-items-overdue - List every open or overdue incident action item across all incidents, grouped by owner or team, with incident, severity, and age.

  Reach for this in the weekly review to see which post-incident commitments are slipping and who owns them.

  rootly-cli action-items-overdue --group-by owner --agent
  

• digest - Time-windowed rollup of everything that moved since a timestamp: incidents opened/resolved, severity changes, new action items, alerts fired.

  Reach for this after time away or before standup for a portfolio-wide what-moved rollup; use handoff for shift-scoped summaries.

  rootly-cli digest --since 24h --agent
  

On-call operations

• coverage-gaps - Scan every on-call schedule for unstaffed windows over the next N days so you catch holiday and weekend gaps before a page is missed.

  Run this on Monday (or in CI) to find on-call holes proactively rather than after someone misses an alert.

  rootly-cli coverage-gaps --days 14 --agent
  

• oncall-now - Show who is on call right now across every schedule and service in one table, escalation tier included.

  Use when a page fires and you need to know who is responsible across all services without opening each schedule.

  rootly-cli oncall-now --agent
  

• handoff - End-of-shift summary: incidents opened, closed, and still open during the outgoing shift window, plus open action items and severity mix.

  Run at shift change so the next on-call inherits an accurate picture instead of a retyped-from-memory note.

  rootly-cli handoff --schedule primary-oncall --agent
  

• oncall-load - Rank people by on-call hours and pages received across every schedule, so uneven rotations and burnout risk surface before someone quits.

  Reach for this when asked who is overloaded, whether the rotation is fair, or who absorbed the most pages this month.

  rootly-cli oncall-load --days 30 --agent
  

• escalation-trace - Print the full ordered escalation ladder for a service or incident - every rung, the policy it comes from, who currently sits at each level, and the delay before the next page.

  Reach for this during a page to answer 'who is next if nobody acks' without walking four API objects by hand.

  rootly-cli escalation-trace --service checkout-api --agent
  

Reliability analytics

• mttr - Compute mean time to acknowledge and resolve from incident timestamps, grouped by service, team, or severity, with optional volume counts.

  Use for the weekly reliability review or to quantify whether a service is trending worse over time.

  rootly-cli mttr --by service --since 30d --agent
  

• service-health - Per-service scorecard: incident count, MTTR, last incident, open action items, current on-call, and SLA status in one row.

  Pull this before a deploy or during a portfolio review to judge a service's health at a glance.

  rootly-cli service-health <service> --agent
  

• sla-breach - List incidents that have breached or are about to breach their SLA target, sorted by time remaining, with a non-zero exit when any active breach exists.

  Reach for this to gate dashboards or escalations on real SLA risk; exit code makes it pipeline-wireable.

  rootly-cli sla-breach --within 2h --agent
  

CI / deploy plumbing

• deploy-guard - Pre-deploy gate for a service: checks for an open incident, confirms someone is on call, and flags recent flakiness, returning a non-zero exit code when it is unsafe to ship.

  Wire into a deploy script so a risky push is blocked when the target service is mid-incident or has no on-call coverage.

  rootly-cli deploy-guard <service> --within 7d
  

Config & signal hygiene

• config-diff - Diff the current synced Rootly config (services, escalation policies, workflows, severities, schedules) against the last saved snapshot to see what was added, removed, or changed - 'config-diff --save' records the baseline.

  Reach for this when auditing whether live Rootly config drifted from what config-as-code thinks it manages.

  rootly-cli config-diff --agent
  

• alert-noise - Rank alert sources and services by alert volume, repeat-fire rate, and how many alerts never became incidents - the signal-to-noise view that finds a flapping integration.

  Reach for this when on-call is drowning: it names the noisiest source and the alerts that never become real incidents.

  rootly-cli alert-noise --days 14 --agent
  

Command Reference

action-items - Manage action items

• rootly-cli action-items delete-incident - Delete a specific incident action item by id
• rootly-cli action-items get-incident - Retrieves a specific incident_action_item by id
• rootly-cli action-items list-all-incident - List all action items for an organization
• rootly-cli action-items update-incident - Update a specific incident action item by id

alert-events - Manage alert events

• rootly-cli alert-events delete - Deletes a specific alert event. Only alert events with kind 'note' (user-created notes) can be deleted.
• rootly-cli alert-events get - Retrieves a specific alert_event by id
• rootly-cli alert-events update - Updates a specific alert event. Only alert events with kind 'note' (user-created notes) can be updated.

alert-fields - Manage alert fields

• rootly-cli alert-fields create - Creates a new alert field from provided data
• rootly-cli alert-fields delete - Delete a specific alert field by id
• rootly-cli alert-fields get - Retrieves a specific alert field by id
• rootly-cli alert-fields list - List alert fields
• rootly-cli alert-fields update - Update a specific alert field by id

alert-groups - Manage alert groups

• rootly-cli alert-groups create - Creates a new alert group.
• rootly-cli alert-groups delete - Delete a specific alert group by id
• rootly-cli alert-groups get - Retrieves a specific alert group by id
• rootly-cli alert-groups list - List alert groups
• rootly-cli alert-groups update - Update a specific alert group by id.

alert-routes - Manage alert routes

• rootly-cli alert-routes create - Creates a new alert route from provided data. **Note: This endpoint requires access to Advanced Alert Routing.
• rootly-cli alert-routes delete - Delete a specific alert route by id. **Note: This endpoint requires access to Advanced Alert Routing.
• rootly-cli alert-routes get - Get a specific alert route by id. **Note: This endpoint requires access to Advanced Alert Routing.
• rootly-cli alert-routes list - List all alert routes for the current team with filtering and pagination.
• rootly-cli alert-routes patch - Updates an alert route. **Note: This endpoint requires access to Advanced Alert Routing.
• rootly-cli alert-routes update - Update a specific alert route by id. **Note: This endpoint requires access to Advanced Alert Routing.

alert-routing-rules - Manage alert routing rules

• rootly-cli alert-routing-rules create - Creates a new alert routing rule from provided data.
• rootly-cli alert-routing-rules delete - Delete a specific alert routing rule by id.
• rootly-cli alert-routing-rules get - Retrieves a specific alert routing rule by id.
• rootly-cli alert-routing-rules list - List alert routing rules.
• rootly-cli alert-routing-rules update - Update a specific alert routing rule by id.

alert-sources - Manage alert sources

• rootly-cli alert-sources create-alerts-source - Creates a new alert source from provided data
• rootly-cli alert-sources delete-alerts-source - Delete a specific alert source by id
• rootly-cli alert-sources get-alerts-source - Retrieves a specific alert source by id
• rootly-cli alert-sources list-alerts-sources - List alert sources
• rootly-cli alert-sources update-alerts-source - Update a specific alert source by id

alert-urgencies - Manage alert urgencies

• rootly-cli alert-urgencies create-alert-urgency - Creates a new alert urgency from provided data
• rootly-cli alert-urgencies delete-alert-urgency - Delete a specific alert urgency by id
• rootly-cli alert-urgencies get-alert-urgency - Retrieves a specific alert urgency by id
• rootly-cli alert-urgencies list - List alert urgencies
• rootly-cli alert-urgencies update-alert-urgency - Update a specific alert urgency by id

alerts - Manage alerts

• rootly-cli alerts create - Creates a new alert from provided data
• rootly-cli alerts get - Retrieves a specific alert by id
• rootly-cli alerts list - List alerts
• rootly-cli alerts update - Updates an alert

api-keys - Manage api keys

• rootly-cli api-keys create - Creates a new API key and returns it with the plaintext token.
• rootly-cli api-keys delete - Revoke an API key. The key is immediately invalidated and can no longer be used for authentication.
• rootly-cli api-keys get - Retrieves a specific API key by its UUID.
• rootly-cli api-keys list - List API keys for the current organization.
• rootly-cli api-keys update - Update an API key's mutable attributes: name, description, and expires_at.

audits - Manage audits

• rootly-cli audits - List audits

authorizations - Manage authorizations

• rootly-cli authorizations create - Creates a new authorization from provided data
• rootly-cli authorizations delete - Delete a specific authorization by id
• rootly-cli authorizations get - Retrieves a specific authorization by id
• rootly-cli authorizations list - List authorizations
• rootly-cli authorizations update - Update a specific authorization by id

catalog-checklist-templates - Manage catalog checklist templates

• rootly-cli catalog-checklist-templates create - Creates a new catalog checklist template
• rootly-cli catalog-checklist-templates delete - Delete a specific catalog checklist template by id
• rootly-cli catalog-checklist-templates get - Retrieves a specific catalog checklist template by id
• rootly-cli catalog-checklist-templates list - List catalog checklist templates
• rootly-cli catalog-checklist-templates update - Update a specific catalog checklist template by id

catalog-entities - Manage catalog entities

• rootly-cli catalog-entities delete-catalog-entity - Delete a specific Catalog Entity by id
• rootly-cli catalog-entities get-catalog-entity - Retrieves a specific Catalog Entity by id
• rootly-cli catalog-entities update-catalog-entity - Update a specific Catalog Entity by id

catalog-entity-checklists - Manage catalog entity checklists

• rootly-cli catalog-entity-checklists get - Retrieves a specific catalog entity checklist by id
• rootly-cli catalog-entity-checklists list - List catalog entity checklists

catalog-entity-properties - Manage catalog entity properties

• rootly-cli catalog-entity-properties delete-catalog-entity-property - Deprecated: This endpoint is deprecated
• rootly-cli catalog-entity-properties get-catalog-entity-property - Deprecated: This endpoint is deprecated
• rootly-cli catalog-entity-properties update-catalog-entity-property - Deprecated: This endpoint is deprecated

catalog-properties - Manage catalog properties

• rootly-cli catalog-properties delete-catalog-property - Delete a specific catalog_property by id - returns catalog_properties type
• rootly-cli catalog-properties get-catalog-property - Retrieves a specific Catalog Property by id - returns catalog_properties type
• rootly-cli catalog-properties update-catalog-property - Update a specific catalog_property by id - returns catalog_properties type

catalogs - Manage catalogs

• rootly-cli catalogs create - Creates a new catalog from provided data
• rootly-cli catalogs delete - Delete a specific catalog by id
• rootly-cli catalogs get - Retrieves a specific catalog by id
• rootly-cli catalogs list - List catalogs
• rootly-cli catalogs update - Update a specific catalog by id

causes - Manage causes

• rootly-cli causes create - Creates a new cause from provided data
• rootly-cli causes create-catalog-property - Creates a new Catalog Property from provided data
• rootly-cli causes delete - Delete a specific cause by id
• rootly-cli causes get - Retrieves a specific cause by id
• rootly-cli causes list - List causes
• rootly-cli causes list-catalog-properties - List Cause Catalog Properties
• rootly-cli causes update - Update a specific cause by id

communications - Manage communications

• rootly-cli communications create-group - Creates a new communications group from provided data
• rootly-cli communications create-stage - Creates a new communications stage from provided data
• rootly-cli communications create-template - Creates a new communications template from provided data
• rootly-cli communications create-type - Creates a new communications type from provided data
• rootly-cli communications delete-group - Deletes a communications group
• rootly-cli communications delete-stage - Deletes a communications stage
• rootly-cli communications delete-template - Deletes a communications template
• rootly-cli communications delete-type - Deletes a communications type
• rootly-cli communications get-group - Shows details of a communications group
• rootly-cli communications get-stage - Shows details of a communications stage
• rootly-cli communications get-template - Shows details of a communications template
• rootly-cli communications get-type - Shows details of a communications type
• rootly-cli communications list-groups - Lists communications groups
• rootly-cli communications list-stages - Lists communications stages
• rootly-cli communications list-templates - Lists communications templates
• rootly-cli communications list-types - Lists communications types
• rootly-cli communications update-group - Updates a communications group
• rootly-cli communications update-stage - Updates a communications stage
• rootly-cli communications update-template - Updates a communications template
• rootly-cli communications update-type - Updates a communications type

custom-field-options - Manage custom field options

• rootly-cli custom-field-options delete - [DEPRECATED] Use form field endpoints instead. Delete a specific Custom Field Option by id
• rootly-cli custom-field-options get - [DEPRECATED] Use form field endpoints instead. Retrieves a specific custom field option by id
• rootly-cli custom-field-options update - [DEPRECATED] Use form field endpoints instead. Update a specific custom field option by id

custom-fields - Manage custom fields

• rootly-cli custom-fields create - [DEPRECATED] Use form field endpoints instead. Creates a new custom field from provided data
• rootly-cli custom-fields delete - [DEPRECATED] Use form field endpoints instead. Delete a specific custom field by id
• rootly-cli custom-fields get - Retrieves a specific custom_field by id
• rootly-cli custom-fields list - [DEPRECATED] Use form field endpoints instead. List Custom fields
• rootly-cli custom-fields update - [DEPRECATED] Use form field endpoints instead. Update a specific custom field by id

custom-forms - Manage custom forms

• rootly-cli custom-forms create - Creates a new custom form from provided data
• rootly-cli custom-forms delete - Delete a specific custom form by id
• rootly-cli custom-forms get - Retrieves a specific custom form by id
• rootly-cli custom-forms list - List custom forms
• rootly-cli custom-forms update - Update a specific custom form by id

dashboard-panels - Manage dashboard panels

• rootly-cli dashboard-panels delete - Delete a specific dashboard panel by id
• rootly-cli dashboard-panels get - Retrieves a specific dashboard panel by id
• rootly-cli dashboard-panels update - Update a specific dashboard panel by id

dashboards - Manage dashboards

• rootly-cli dashboards create - Creates a new dashboard from provided data
• rootly-cli dashboards delete - Delete a specific dashboard by id
• rootly-cli dashboards get - Retrieves a specific dashboard by id
• rootly-cli dashboards list - List dashboards
• rootly-cli dashboards update - Update a specific dashboard by id

edge-connectors - Manage edge connectors

• rootly-cli edge-connectors create - Create edge connector
• rootly-cli edge-connectors delete - Delete edge connector
• rootly-cli edge-connectors get - Show edge connector
• rootly-cli edge-connectors list - List edge connectors
• rootly-cli edge-connectors update - Update edge connector

email-addresses - Manage email addresses

• rootly-cli email-addresses delete-user-email-address - Deletes a user email address
• rootly-cli email-addresses show-user-email-address - Retrieves a specific user email address
• rootly-cli email-addresses update-user-email-address - Updates a user email address

environments - Manage environments

• rootly-cli environments create - Creates a new environment from provided data
• rootly-cli environments create-catalog-property - Creates a new Catalog Property from provided data
• rootly-cli environments delete - Delete a specific environment by id
• rootly-cli environments get - Retrieves a specific environment by id
• rootly-cli environments list - List environments
• rootly-cli environments list-catalog-properties - List Environment Catalog Properties
• rootly-cli environments update - Update a specific environment by id

escalation-levels - Manage escalation levels

• rootly-cli escalation-levels delete - Delete a specific escalation level by id
• rootly-cli escalation-levels get - Retrieves a specific escalation level by id
• rootly-cli escalation-levels update - Update a specific escalation level by id

escalation-paths - Manage escalation paths

• rootly-cli escalation-paths delete - Delete a specific escalation path by id
• rootly-cli escalation-paths get - Retrieves a specific escalation path by id
• rootly-cli escalation-paths update - Update a specific escalation path by id

escalation-policies - Manage escalation policies

• rootly-cli escalation-policies create-escalation-policy - Creates a new escalation policy from provided data
• rootly-cli escalation-policies delete-escalation-policy - Delete a specific escalation policy by id
• rootly-cli escalation-policies get-escalation-policy - Retrieves a specific escalation policy by id
• rootly-cli escalation-policies list - List escalation policies
• rootly-cli escalation-policies update-escalation-policy - Update a specific escalation policy by id

events - Manage events

• rootly-cli events delete-incident - Delete a specific incident event by id
• rootly-cli events get-incident - Retrieves a specific incident_event by id
• rootly-cli events update-incident - Update a specific incident event by id

feedbacks - Manage feedbacks

• rootly-cli feedbacks get-incident - Retrieves a specific incident_feedback by id
• rootly-cli feedbacks update-incident - Update a specific incident feedback by id

form-field-options - Manage form field options

• rootly-cli form-field-options delete - Delete a specific form_field_option by id
• rootly-cli form-field-options get - Retrieves a specific form_field_option by id
• rootly-cli form-field-options update - Update a specific form_field_option by id

form-field-placement-conditions - Manage form field placement conditions

• rootly-cli form-field-placement-conditions delete - Delete a specific form_field_placement_condition by id
• rootly-cli form-field-placement-conditions get - Retrieves a specific form_field_placement_condition by id
• rootly-cli form-field-placement-conditions update - Update a specific form_field_placement_condition by id

form-field-placements - Manage form field placements

• rootly-cli form-field-placements delete - Delete a specific form_field_placement by id
• rootly-cli form-field-placements get - Retrieves a specific form_field_placement by id
• rootly-cli form-field-placements update - Update a specific form_field_placement by id

form-field-positions - Manage form field positions

• rootly-cli form-field-positions delete - Delete a specific form_field position by id
• rootly-cli form-field-positions get - Retrieves a specific form field_position by id
• rootly-cli form-field-positions update - Update a specific form_field position by id

form-fields - Manage form fields

• rootly-cli form-fields create - Creates a new form_field from provided data
• rootly-cli form-fields delete - Delete a specific form_field by id
• rootly-cli form-fields get - Retrieves a specific form_field by id
• rootly-cli form-fields list - List form_fields
• rootly-cli form-fields update - Update a specific form_field by id

form-set-conditions - Manage form set conditions

• rootly-cli form-set-conditions delete - Delete a specific form_set_condition by id
• rootly-cli form-set-conditions get - Retrieves a specific form_set_condition by id
• rootly-cli form-set-conditions update - Update a specific form_set_condition by id

form-sets - Manage form sets

• rootly-cli form-sets create - Creates a new form_set from provided data
• rootly-cli form-sets delete - Delete a specific form_set by id
• rootly-cli form-sets get - Retrieves a specific form_set by id
• rootly-cli form-sets list - List form_sets
• rootly-cli form-sets update - Update a specific form_set by id

functionalities - Manage functionalities

• rootly-cli functionalities create-functionality - Creates a new functionality from provided data
• rootly-cli functionalities create-functionality-catalog-property - Creates a new Catalog Property from provided data
• rootly-cli functionalities delete-functionality - Delete a specific functionality by id
• rootly-cli functionalities get-functionality - Retrieves a specific functionality by id
• rootly-cli functionalities list - List functionalities
• rootly-cli functionalities list-functionality-catalog-properties - List Functionality Catalog Properties
• rootly-cli functionalities update-functionality - Update a specific functionality by id

heartbeats - Manage heartbeats

• rootly-cli heartbeats create - Creates a new heartbeat from provided data
• rootly-cli heartbeats delete - Delete a specific heartbeat by id
• rootly-cli heartbeats get - Retrieves a specific heartbeat by id
• rootly-cli heartbeats list - List heartbeats
• rootly-cli heartbeats update - Update a specific heartbeat by id

incident-custom-field-selections - Manage incident custom field selections

• rootly-cli incident-custom-field-selections delete - [DEPRECATED] Use form field endpoints instead. Delete a specific incident custom field selection by id
• rootly-cli incident-custom-field-selections get - [DEPRECATED] Use form field endpoints instead. Retrieves a specific incident custom field selection by id
• rootly-cli incident-custom-field-selections update - [DEPRECATED] Use form field endpoints instead. Update a specific incident custom field selection by id

incident-event-functionalities - Manage incident event functionalities

• rootly-cli incident-event-functionalities delete-incident-event-functionality - Delete a specific incident event functionality by id
• rootly-cli incident-event-functionalities get - Retrieves a specific incident_event_functionality by id
• rootly-cli incident-event-functionalities update-incident-event-functionality - Update a specific incident event functionality by id

incident-event-services - Manage incident event services

• rootly-cli incident-event-services delete - Delete a specific incident event service by id
• rootly-cli incident-event-services get - Retrieves a specific incident_event_service by id
• rootly-cli incident-event-services update - Update a specific incident event service by id

incident-form-field-selections - Manage incident form field selections

• rootly-cli incident-form-field-selections delete - Delete a specific incident form field selection by id
• rootly-cli incident-form-field-selections get - Retrieves a specific incident form field selection by id
• rootly-cli incident-form-field-selections update - Update a specific incident form field selection by id

incident-permission-set-booleans - Manage incident permission set booleans

• rootly-cli incident-permission-set-booleans delete - Delete a specific incident_permission_set_boolean by id
• rootly-cli incident-permission-set-booleans get - Retrieves a specific incident_permission_set_boolean by id
• rootly-cli incident-permission-set-booleans update - Update a specific incident_permission_set_boolean by id

incident-permission-set-resources - Manage incident permission set resources

• rootly-cli incident-permission-set-resources delete - Delete a specific incident_permission_set_resource by id
• rootly-cli incident-permission-set-resources get - Retrieves a specific incident_permission_set_resource by id
• rootly-cli incident-permission-set-resources update - Update a specific incident_permission_set_resource by id

incident-permission-sets - Manage incident permission sets

• rootly-cli incident-permission-sets create - Creates a new incident_permission_set from provided data
• rootly-cli incident-permission-sets delete - Delete a specific incident_permission_set by id
• rootly-cli incident-permission-sets get - Retrieves a specific incident_permission_set by id
• rootly-cli incident-permission-sets list - List incident_permission_sets
• rootly-cli incident-permission-sets update - Update a specific incident_permission_set by id

incident-retrospective-steps - Manage incident retrospective steps

• rootly-cli incident-retrospective-steps get - Retrieves a specific incident retrospective step by id
• rootly-cli incident-retrospective-steps update - Update a specific incident retrospective step by id

incident-role-tasks - Manage incident role tasks

• rootly-cli incident-role-tasks delete - Delete a specific incident_role task by id
• rootly-cli incident-role-tasks get - Retrieves a specific incident_role_task by id
• rootly-cli incident-role-tasks update - Update a specific incident_role task by id

incident-roles - Manage incident roles

• rootly-cli incident-roles create - Creates a new incident role from provided data
• rootly-cli incident-roles delete - Delete a specific incident_role by id
• rootly-cli incident-roles get - Retrieves a specific incident_role by id
• rootly-cli incident-roles list - List incident roles
• rootly-cli incident-roles update - Update a specific incident_role by id

incident-sub-statuses - Manage incident sub statuses

• rootly-cli incident-sub-statuses delete-incident-sub-status - Delete a specific incident_sub_status by id
• rootly-cli incident-sub-statuses get-incident-sub-status - Retrieves a specific incident_sub_status by id
• rootly-cli incident-sub-statuses update-incident-sub-status - Update a specific incident_sub_status by id

incident-types - Manage incident types

• rootly-cli incident-types create - Creates a new incident_type from provided data
• rootly-cli incident-types create-catalog-property - Creates a new Catalog Property from provided data
• rootly-cli incident-types delete - Delete a specific incident_type by id
• rootly-cli incident-types get - Retrieves a specific incident_type by id
• rootly-cli incident-types list - List incident types
• rootly-cli incident-types list-catalog-properties - List IncidentType Catalog Properties
• rootly-cli incident-types update - Update a specific incident_type by id

incidents - Manage incidents

• rootly-cli incidents create - Creates a new incident from provided data
• rootly-cli incidents delete - Delete a specific incident by id
• rootly-cli incidents get - Retrieves a specific incident by id
• rootly-cli incidents list - List incidents
• rootly-cli incidents update - Update a specific incident by id

ip-ranges - Manage ip ranges

• rootly-cli ip-ranges - Retrieves the IP ranges for rootly.com services

live-call-routers - Manage live call routers

• rootly-cli live-call-routers create - Creates a new Live Call Router from provided data
• rootly-cli live-call-routers delete - Delete a specific Live Call Router by id
• rootly-cli live-call-routers generate-phone-number - Generates a phone number for Live Call Router
• rootly-cli live-call-routers get - Retrieves a specific Live Call Router by id
• rootly-cli live-call-routers list - List Live Call Routers
• rootly-cli live-call-routers update - Update a specific Live Call Router by id

meeting-recordings - Manage meeting recordings

• rootly-cli meeting-recordings delete - Delete a meeting recording. Only completed or failed recordings can be deleted.
• rootly-cli meeting-recordings get - Retrieve a single meeting recording session including its status, duration, speaker count, word count

notification-rules - Manage notification rules

• rootly-cli notification-rules delete-user - Delete a specific user notification rule by id
• rootly-cli notification-rules get-user - Retrieves a specific user notification rule by id
• rootly-cli notification-rules update-user - Update a specific user notification rule by id

on-call-pay-reports - Manage on call pay reports

• rootly-cli on-call-pay-reports create - Generates a new on-call pay report for the given date range. The report is generated asynchronously.
• rootly-cli on-call-pay-reports get - Retrieves a specific on-call pay report by id
• rootly-cli on-call-pay-reports list - List on-call pay reports
• rootly-cli on-call-pay-reports update - Update a specific on-call pay report by id. Triggers report regeneration.

on-call-roles - Manage on call roles

• rootly-cli on-call-roles create - Creates a new On-Call Role from provided data
• rootly-cli on-call-roles delete - Delete a specific On-Call Role by id
• rootly-cli on-call-roles get - Retrieves a specific On-Call Role by id
• rootly-cli on-call-roles list - List On-Call Roles
• rootly-cli on-call-roles update - Update a specific On-Call Role by id

on-call-shadows - Manage on call shadows

• rootly-cli on-call-shadows delete - Delete a specific on call shadow configuration by id. Future shadows are hard-deleted.
• rootly-cli on-call-shadows get - Retrieves a specific On Call Shadow configuration by ID
• rootly-cli on-call-shadows update - Update a specific on call shadow configuration by id

oncalls - Manage oncalls

• rootly-cli oncalls - List who is currently on-call, with support for filtering by escalation policy, schedule, and user.

override-shifts - Manage override shifts

• rootly-cli override-shifts delete - Delete a specific override shift by id
• rootly-cli override-shifts get - Retrieves a specific override shift by id
• rootly-cli override-shifts update - Update a specific override shift by id

phone-numbers - Manage phone numbers

• rootly-cli phone-numbers delete-user - Deletes a user phone number
• rootly-cli phone-numbers show-user - Retrieves a specific user phone number
• rootly-cli phone-numbers update-user - Updates a user phone number

playbook-tasks - Manage playbook tasks

• rootly-cli playbook-tasks delete - Delete a specific playbook task by id
• rootly-cli playbook-tasks get - Retrieves a specific playbook_task by id
• rootly-cli playbook-tasks update - Update a specific playbook task by id

playbooks - Manage playbooks

• rootly-cli playbooks create - Creates a new playbook from provided data
• rootly-cli playbooks delete - Delete a specific playbook by id
• rootly-cli playbooks get - Retrieves a specific playbook by id
• rootly-cli playbooks list - List playbooks
• rootly-cli playbooks update - Update a specific playbook by id

post-mortem-templates - Manage post mortem templates

• rootly-cli post-mortem-templates create-postmortem-template - Creates a new Retrospective Template from provided data
• rootly-cli post-mortem-templates delete-postmortem-template - Delete a specific Retrospective Template by id
• rootly-cli post-mortem-templates get-postmortem-template - Retrieves a specific Retrospective Template by id
• rootly-cli post-mortem-templates list-postmortem-templates - List Retrospective Templates
• rootly-cli post-mortem-templates update-postmortem-template - Update a specific Retrospective Template by id

post-mortems - Manage post mortems

• rootly-cli post-mortems list-incident - List incident retrospectives
• rootly-cli post-mortems list-incident-postmortems - Retrieves an incident retrospective
• rootly-cli post-mortems update-incident - Update a specific incident retrospective by id

pulses - Manage pulses

• rootly-cli pulses create - Creates a new pulse from provided data
• rootly-cli pulses get - Retrieves a specific pulse by id
• rootly-cli pulses list - List pulses
• rootly-cli pulses update - Update a specific pulse by id

retrospective-configurations - Manage retrospective configurations

• rootly-cli retrospective-configurations get - Retrieves a specific retrospective_configuration by id
• rootly-cli retrospective-configurations list - List retrospective configurations
• rootly-cli retrospective-configurations update - Update a specific retrospective configuration by id

retrospective-process-group-steps - Manage retrospective process group steps

• rootly-cli retrospective-process-group-steps delete - Delete a specific RetrospectiveProcessGroup Step by id
• rootly-cli retrospective-process-group-steps get - Retrieves a specific RetrospectiveProcessGroup Step by id
• rootly-cli retrospective-process-group-steps update - Update a specific RetrospectiveProcessGroup Step by id

retrospective-process-groups - Manage retrospective process groups

• rootly-cli retrospective-process-groups delete - Delete a specific Retrospective Process Group by id
• rootly-cli retrospective-process-groups get - Retrieves a specific Retrospective Process Group by id
• rootly-cli retrospective-process-groups update - Update a specific Retrospective Process Group by id

retrospective-processes - Manage retrospective processes

• rootly-cli retrospective-processes create-retrospective-process - Creates a new retrospective process from provided data
• rootly-cli retrospective-processes delete-retrospective-process - Delete a specific retrospective process by id
• rootly-cli retrospective-processes get-retrospective-process - Retrieves a specific retrospective process by id
• rootly-cli retrospective-processes list - List retrospective processes
• rootly-cli retrospective-processes update-retrospective-process - Updates a specific retrospective process by id

retrospective-steps - Manage retrospective steps

• rootly-cli retrospective-steps delete - Delete a specific retrospective step by id
• rootly-cli retrospective-steps get - Retrieves a specific retrospective step by id
• rootly-cli retrospective-steps update - Update a specific retrospective step by id

roles - Manage roles

• rootly-cli roles create - Creates a new role from provided data
• rootly-cli roles delete - Delete a specific role by id
• rootly-cli roles get - Retrieves a specific role by id
• rootly-cli roles list - List roles
• rootly-cli roles update - Update a specific role by id

schedule-rotation-active-days - Manage schedule rotation active days

• rootly-cli schedule-rotation-active-days delete - Delete a specific schedule rotation active day
• rootly-cli schedule-rotation-active-days get - Retrieves a specific schedule rotation active day by id
• rootly-cli schedule-rotation-active-days update - Update a specific schedule rotation active day by id

schedule-rotation-users - Manage schedule rotation users

• rootly-cli schedule-rotation-users delete - Delete a specific schedule rotation user by id
• rootly-cli schedule-rotation-users get - Retrieves a specific schedule rotation user by id
• rootly-cli schedule-rotation-users update - Update a specific schedule rotation user by id

schedule-rotations - Manage schedule rotations

• rootly-cli schedule-rotations delete - Delete a specific schedule rotation by id
• rootly-cli schedule-rotations get - Retrieves a specific schedule rotation by id
• rootly-cli schedule-rotations update - Update a specific schedule rotation by id

schedules - Manage schedules

• rootly-cli schedules create - Creates a new schedule from provided data
• rootly-cli schedules delete - Delete a specific schedule by id
• rootly-cli schedules get - Retrieves a specific schedule by id
• rootly-cli schedules list - List schedules
• rootly-cli schedules update - Updates a specific schedule by id

secrets - Manage secrets

• rootly-cli secrets create - Creates a new secret from provided data
• rootly-cli secrets delete - Delete a specific secret by id
• rootly-cli secrets get - Retrieve a specific secret by id
• rootly-cli secrets list - List secrets
• rootly-cli secrets update - Update a specific secret by id

services - Manage services

• rootly-cli services create - Creates a new service from provided data
• rootly-cli services create-catalog-property - Creates a new Catalog Property from provided data
• rootly-cli services delete - Delete a specific service by id
• rootly-cli services get - Retrieves a specific service by id
• rootly-cli services list - List services
• rootly-cli services list-catalog-properties - List Service Catalog Properties
• rootly-cli services update - Update a specific service by id

severities - Manage severities

• rootly-cli severities create-severity - Creates a new severity from provided data
• rootly-cli severities delete-severity - Delete a specific severity by id
• rootly-cli severities get-severity - Retrieves a specific severity by id
• rootly-cli severities list - List severities
• rootly-cli severities update-severity - Update a specific severity by id

shifts - Manage shifts

• rootly-cli shifts - List shifts

slas - Manage slas

• rootly-cli slas create - Creates a new SLA from provided data
• rootly-cli slas delete - Delete a specific SLA by id
• rootly-cli slas get - Retrieves a specific SLA by id
• rootly-cli slas list - List SLAs
• rootly-cli slas update - Update a specific SLA by id

status-page-events - Manage status page events

• rootly-cli status-page-events delete-incident-status-page - Delete a specific incident status page event by id
• rootly-cli status-page-events get-incident-status-pages - Retrieves a specific incident_status_page_event by id
• rootly-cli status-page-events update-incident-status-page - Update a specific incident status page event by id

status-pages - Manage status pages

• rootly-cli status-pages create - Creates a new status page from provided data
• rootly-cli status-pages delete - Delete a specific status page by id
• rootly-cli status-pages get - Retrieves a specific status page by id
• rootly-cli status-pages list - List status pages
• rootly-cli status-pages update - Update a specific status page by id

statuses - Manage statuses

• rootly-cli statuses get-status - Retrieves a specific Status by id
• rootly-cli statuses list - List Statuses

sub-statuses - Manage sub statuses

• rootly-cli sub-statuses create-sub-status - Creates a new Sub-Status from provided data
• rootly-cli sub-statuses delete-sub-status - Delete a specific Sub-Status by id
• rootly-cli sub-statuses get-sub-status - Retrieves a specific Sub-Status by id
• rootly-cli sub-statuses list - List Sub-Statuses
• rootly-cli sub-statuses update-sub-status - Update a specific Sub-Status by id

teams - Manage teams

• rootly-cli teams create - Creates a new team from provided data
• rootly-cli teams create-group-catalog-property - Creates a new Catalog Property from provided data
• rootly-cli teams delete - Delete a specific team by id
• rootly-cli teams get - Retrieves a specific team by id
• rootly-cli teams list - List teams
• rootly-cli teams list-group-catalog-properties - List Group Catalog Properties
• rootly-cli teams update - Update a specific team by id

templates - Manage templates

• rootly-cli templates delete-status-page - Delete a specific template event by id
• rootly-cli templates get-status-page - Retrieves a specific status_page_template by id
• rootly-cli templates update-status-page - Update a specific template event by id

users - Manage users

• rootly-cli users delete - Delete a specific user by id
• rootly-cli users get - Retrieves a specific user by id
• rootly-cli users get-current - Get current user
• rootly-cli users list - List users
• rootly-cli users update - Update a specific user by id

webhooks - Manage webhooks

• rootly-cli webhooks create-endpoint - Creates a new webhook endpoint from provided data
• rootly-cli webhooks delete-endpoint - Delete a specific webhook endpoint by id
• rootly-cli webhooks deliver-delivery - Retries a webhook delivery
• rootly-cli webhooks get-delivery - Retrieves a specific webhook delivery by id
• rootly-cli webhooks get-endpoint - Retrieves a specific webhook endpoint by id
• rootly-cli webhooks list-deliveries - List webhook deliveries for given endpoint
• rootly-cli webhooks list-endpoints - List webhook endpoints
• rootly-cli webhooks update-endpoint - Update a specific webhook endpoint by id

workflow-custom-field-selections - Manage workflow custom field selections

• rootly-cli workflow-custom-field-selections delete - [DEPRECATED] Use form field endpoints instead. Delete a specific workflow custom field selection by id
• rootly-cli workflow-custom-field-selections get - [DEPRECATED] Use form field endpoints instead. Retrieves a specific workflow custom field selection by id
• rootly-cli workflow-custom-field-selections update - [DEPRECATED] Use form field endpoints instead. Update a specific workflow custom field selection by id

workflow-form-field-conditions - Manage workflow form field conditions

• rootly-cli workflow-form-field-conditions delete - Delete a specific workflow form field condition by id
• rootly-cli workflow-form-field-conditions get - Retrieves a specific workflow form field condition by id
• rootly-cli workflow-form-field-conditions update - Update a specific workflow form field condition by id

workflow-groups - Manage workflow groups

• rootly-cli workflow-groups create - Creates a new workflow group from provided data
• rootly-cli workflow-groups delete - Delete a specific workflow group by id
• rootly-cli workflow-groups get - Retrieves a specific workflow group by id
• rootly-cli workflow-groups list - List workflow groups
• rootly-cli workflow-groups update - Update a specific workflow group by id

workflow-tasks - Manage workflow tasks

• rootly-cli workflow-tasks delete - Delete a specific workflow task by id
• rootly-cli workflow-tasks get - Retrieves a specific workflow_task by id
• rootly-cli workflow-tasks update - Update a specific workflow task by id

workflows - Manage workflows

• rootly-cli workflows create - Creates a new workflow from provided data
• rootly-cli workflows delete - Delete a specific workflow by id
• rootly-cli workflows get - Retrieves a specific workflow by id
• rootly-cli workflows list - List workflows
• rootly-cli workflows update - Update a specific workflow by id

Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

rootly-cli which "<capability in your own words>"

which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match - fall back to --help or use a narrower query.

Recipes

Triage a familiar-looking incident

rootly-cli related INC-1234 --agent --limit 5

Surface the five most similar past incidents so you can reuse a known resolution path.

Narrow a verbose incident list for an agent

rootly-cli incidents list --agent --select data.id,data.attributes.title,data.attributes.created_at,data.attributes.severity

JSON:API returns tens of KB per call; dotted --select returns only the fields an agent needs so it does not burn context parsing the rest.

Find Monday's on-call holes

rootly-cli coverage-gaps --days 14 --agent

Report every unstaffed on-call window in the next two weeks across all schedules before a page is missed.

Gate a deploy on service health

rootly-cli deploy-guard <service> --within 7d

Exit non-zero when checkout-api has an open incident, no on-call, or recent flakiness - drop it into a deploy script.

Build the weekly reliability review

rootly-cli service-health --agent

Emit a per-service scorecard (incidents, MTTR, open action items, on-call, SLA) for the whole portfolio in one pass.

Auth Setup

Set a Rootly API key as ROOTLY_API_KEY (the same variable the official rootly-cli uses; ROOTLY_API_TOKEN is also accepted). Keys come in Global, Team, and Personal scopes from your Rootly account settings; the CLI sends it as a Bearer token over JSON:API. No tenant or org id is needed - the key identifies the workspace. Run rootly-cli doctor to confirm the key is valid and the API is reachable.

Agent Mode

Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.

• Pipeable - JSON on stdout, errors on stderr

• Filterable - --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:

  rootly-cli alert-events get <id> --agent --select id,name,status
  

• Previewable - --dry-run shows the request without sending

• Offline-friendly - sync/search commands can use the local SQLite store when available

• Non-interactive - never prompts, every input is a flag

• Explicit retries - use --idempotent only when an already-existing create should count as success, and --ignore-missing only when a missing delete target should count as success

Response envelope

Commands that read from the local store or the API wrap output in a provenance envelope:

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set - piped/agent consumers and explicit-format runs get pure JSON on stdout.

Agent Feedback

When you (or the agent) notice something off about this CLI, record it:

rootly-cli feedback "the --since flag is inclusive but docs say exclusive"
rootly-cli feedback --stdin < notes.txt
rootly-cli feedback list --json --limit 10

Entries are stored locally at ~/.local/share/rootly-cli/feedback.jsonl. They are never POSTed unless ROOTLY_FEEDBACK_ENDPOINT is set AND either --send is passed or ROOTLY_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.

Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.

Output Delivery

Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:

Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.

Named Profiles

A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.

rootly-cli profile save briefing --json
rootly-cli --profile briefing alert-events get <id>
rootly-cli profile list --json
rootly-cli profile show briefing
rootly-cli profile delete briefing --yes

Explicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.

Exit Codes

Argument Parsing

Parse $ARGUMENTS:

1. Empty, help, or --help → show rootly-cli --help output
2. Starts with install → ends with mcp → MCP installation; otherwise → see Prerequisites above
3. Anything else → Direct Use (execute as CLI command with --agent)

MCP Server Installation

1. Install the MCP server:

   go install github.com/mvanhorn/printing-press-library/library/monitoring/rootly/cmd/rootly-mcp@latest
   

2. Register with Claude Code:

   claude mcp add rootly-mcp -- rootly-mcp
   

3. Verify: claude mcp list

Direct Use

1. Check if installed: which rootly-cli If not found, offer to install (see Prerequisites at the top of this skill).
2. Match the user query to the best command from the Unique Capabilities and Command Reference above.
3. Execute with the --agent flag:

   rootly-cli <command> [subcommand] [args] --agent
   

4. If ambiguous, drill into subcommand help: rootly-cli <command> --help.