What problem does it solve? Managing Argos alarm rules across multiple regional control planes (CN, I18N, TTP, BOE) requires knowing different gateways, JWT scopes, and API endpoints. This Skill lets you list, inspect, create, update, and delete alarm rules for PSMs you own through a single gdpa-cli interface, with a mandatory two-phase confirmation flow that prevents accidental write operations. ## Core Features & Use Cases - Rule CRUD across regions: List, get, create, update, and delete alarm rules by PSM or rule UID across CN / I18N / TTP / BOE control planes with automatic vregion-to-gateway mapping. - Safe two-phase writes: Every create/update/delete runs a preview phase first showing the exact request, and only executes after explicit user confirmation with confirm: true. - Lark notification configuration: A dedicated reference covers routing alerts to Lark groups, LarkBot webhooks, escalation chains, and receiver_mode decision matrices. - Use Case: You own the PSM ies.gdp.open_api in Singapore and want to check why it is not alerting. List its rules, inspect thresholds and receivers, then update the rule level after previewing the change. ## Quick Start Ask the agent to list all Argos alarm rules for your PSM in the sg region, for example: "List the alarm rules for psm ies.gdp.open_api in sg and show their thresholds and receivers."
