Gateway ops observability

Skill sarveshsea/design-skills/skills/gateway-ops-observability

Practical design judgment for AI coding agents: 78 installable skills for craft, research, generation, Figma, and Memoire.

Install

npx -y skills add sarveshsea/design-skills --skill gateway-ops-observability

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Observe and debug local agent gateways, daemons, health probes, logs, and usage costs.

SKILL.md

1.0 KB, as published. Nobody here has run it

Gateway Ops Observability

Observe and debug local agent gateways, daemons, health probes, logs, and usage costs.

When to Use

Use this Note when a Memoire or Studio run needs gateway logs, agent health, daemon status, usage cost, ops troubleshooting.

Workflow

Check daemon status, gateway health, model auth, and channel connectivity before debugging prompts.
Collect logs with timestamps and session ids so failures can be tied to a specific agent turn.
Record usage cost and quota state when provider limits or slowdowns are plausible.
Distinguish cached health snapshots from live probes in reports.
When a gateway is unhealthy, stop new tasks before restarting or changing config.

Sources

Gives 0 of the 12 instructions most monitoring observability skills give

Counted across 481 of the 483 authors here whose files we hold, read 2026-08-06

link every alert to a runbookin 43 of 481, across 35 files
use structured json loggingin 36 of 481, across 31 files
alert on user-facing symptomsin 20 of 481, across 15 files
emit structured JSON logs with stable event namesin 18 of 481, across 13 files
propagate trace context across boundariesin 16 of 481
use histograms for latency trackingin 14 of 481, across 9 files
use OpenTelemetry for distributed tracingin 13 of 481, across 8 files
include a correlation ID on every log linein 13 of 481, across 8 files
Define service level objectivesin 10 of 481, across 7 files
Call useAzureMonitor before importing other modulesin 9 of 481, across 2 files
stop and ask for clarification if inputs are missingin 9 of 481, across 2 files
define on-call questions before adding telemetryin 9 of 481, across 4 files

Said here and by no other author read

check daemon status and gateway health first
collect logs with timestamps and session ids
record usage cost and quota state
distinguish cached snapshots from live probes
stop new tasks before restarting unhealthy gateways

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.