agentleFS
nassaj2011nassaj2011/claude-skills-for-chatgpt/skills/observability-monitoring/SKILL.md

observability-monitoring

Skill0 starsChanged 27 days agoMITView on GitHub

Plan product telemetry, health checks, logs, metrics, traces, SLOs and incident response for live platforms.

6 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use frontend-design.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add distributed tracing where cross-service latency/root-cause analysis warrants it.

    line 10
  2. Distinctive:

    Verify alerts and recovery drills in a safe environment, then capture gaps and rollback triggers.

    line 13
  3. Distinctive:

    Do not claim monitoring is operational merely because instrumentation code exists.

    line 16
  4. Very specific:

    Run python examples/observability-gate/gate.py --sample examples/observability-gate/sample.jsonl and python -m unittest discover -s …

    line 20

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Observability and operations

  1. Define user-critical outcomes and failure modes. Choose meaningful golden signals: latency, traffic, errors and saturation plus business integrity metrics.
  2. Design structured logs with correlation IDs and appropriate privacy redaction. Distinguish debug logs from audit records.
  3. Define metrics with stable labels/cardinality, units, sample rates, ownership, targets and alert thresholds justified by impact.
  4. Add distributed tracing where cross-service latency/root-cause analysis warrants it; avoid tracing secrets or personal payloads.
  5. Specify probes, dashboards, on-call runbooks, incident severity and escalation; route alerts to an accountable owner.
  6. Define SLO/error budget for critical journeys when evidence supports a measurable target.
  7. Verify alerts and recovery drills in a safe environment, then capture gaps and rollback triggers.

Output: telemetry contract, dashboard panels, alerts, runbook, test evidence and costs. Do not claim monitoring is operational merely because instrumentation code exists.

Offline SLO calculation specimen

Run python examples/observability-gate/gate.py --sample examples/observability-gate/sample.jsonl and python -m unittest discover -s examples/observability-gate -p "test_*.py" -v. These are synthetic sanitized request samples; the calculated 95th percentile and error budget do not prove operational telemetry, production SLO attainment or release readiness.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.