Index of every page on this site: llms.txt
All skills
Run it yourself

Instruments a feature so on-call can tell that it broke, where time went, and why, using logs, metrics, and traces, and designs symptom alerts. Includes a measured performance loop and caching rules. Use when adding logging, logs, structured logs, metrics, tracing, OpenTelemetry, spans, a correlation or request ID, alerts, an SLO, or on-call, when asking how we will know it broke, when instrumenting a feature, endpoint, job, or integration, or when the user mentions performance, a slow endpoint, latency, profiling, optimize, or caching. Not for diagnosing a live incident - use the debug skill where installed; not for creating alerts or dashboards in a specific backend - use that backend's skill; not for database query tuning - use database.

  • 5 files
  • 19.1 KB
  • Updated 3 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/avik-creator/agent-skills/observability

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesalerts.md

≈455 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Alerts

Read when writing or changing an alert. Creating the alert object, the dashboard, or a saved view in a real backend is that backend's skill. Hand it over after a yes, with the rules below as the brief. Why: a page to a shared channel is outward-facing.

Symptom, two severities

Page on what a user would feel: error rate, a latency percentile, how old the oldest queued job is. A cause (CPU, a restart, disk) goes on a dashboard. Why: a cause page fires when users are fine, and stays quiet for a failure you did not predict.

Two severities:

  • Page. Users are affected now. Someone acts.
  • Ticket. Degraded. Someone acts on this week's queue.

A third severity becomes a channel people mute.

The threshold

The threshold and how long it must stay true come from an SLO or from this service's history. Write the source next to the alert ("error budget for the checkout SLO", "p95 over the last 30 days plus the headroom we agreed"). A number you picked because it looks serious is a guess. Delete it and ask. For an SLO-based threshold, use the burn-rate windows in slo.md.

Every alert is actionable. If the response is to wait for it to clear, delete the alert.

Runbook

Link a runbook. The shape is the one in design-docs references/documentation.md: the symptom someone sees, the checks in order, the fix, how to confirm it worked, and who to call. Do not invent a second format. Write each check as a command to run or a place to look.

Test-fire

Fire the new alert once, against the channel it will use, and open the runbook link from the message. A threshold you lowered for the test goes back. Why: an alert that never fired is a wish.

Do this in the backend's own skill when that skill is what creates the object. This skill stops at the rule and the handoff.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at a0324a3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated 3 weeks ago

README badge

README badge for avik-creator/agent-skills/observability