agentleFS
mihaimurra001mihaimurra001/preConfigProject/.agents/skills/observability-and-structured-logging/SKILL.md

observability-and-structured-logging

Skill1 starsChanged 2 months agoMITView on GitHub

Use when adding logging, monitoring, metrics, health checks, or tracing. Enforces structured JSON and distributed context propagation.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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. Very specific:

    Never output unstructured string text (console.log("user logged in: " + user)).

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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, Structured Logging & Health

Production systems must be observable without attaching a remote debugger:

1. Structured JSON Logging

  • Never output unstructured string text (console.log("user logged in: " + user)).
  • Log JSON payloads with standard keys:
    {
      "timestamp": "2026-09-13T21:40:00.000Z",
      "level": "info",
      "message": "User session authenticated",
      "service": "auth-service",
      "trace_id": "4bf92f3577b34da6a3ce929d0e0e4736",
      "span_id": "00f067aa0ba902b7",
      "user_id": "usr_98124",
      "duration_ms": 14.2
    }

2. Request Correlation & Context Propagation

  • Extract or generate an x-request-id header at the API boundary.
  • Propagate the request ID through async context and include it in all outbound HTTP/RPC client calls.

3. Production Health Probes

  • Implement standardized health endpoints:
    • /healthz (Liveness): Returns 200 if the process event loop is responsive.
    • /readyz (Readiness): Returns 200 only if critical dependencies (database, message queue) are connected and ready to accept traffic.

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.