Claude Cursor Skill

observability-standards

Observability standards: JSON structured logging with key=value fields and never string interpolation, the ERROR/WARN/INFO/DEBUG/TRACE level taxonomy, a /health endpoint with per-component status wired to orchestrator probes, counter/gauge/histogram metric choice with no high-car

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download goldziher-ai-rulez-internal_builtins_universal_observability_skills_observability-standards-ca967ad.zip · 0 KB
Part of goldziher/ai-rulez — 151 skills

Install

skills CLI npx skills add https://github.com/Goldziher/ai-rulez/tree/main/internal/builtins/universal/observability/skills/observability-standards
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install goldziher-ai-rulez@llmmart
Git git clone https://github.com/Goldziher/ai-rulez.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole goldziher/ai-rulez collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

  • Structured logging: JSON output, key=value pairs — never string interpolation in log messages.
  • Log levels: ERROR (unrecoverable), WARN (degraded), INFO (state changes), DEBUG (flow), TRACE (off in prod).
  • Health endpoints: /health with component status, wired to orchestrator probes.
  • Metrics: counters for requests, gauges for connections, histograms for latency — no high-cardinality labels.
  • Propagate request/correlation IDs across service boundaries.
Files (ai-rulez)
  • SKILL.md 1009 B
    ---
    name: observability-standards
    description: "Observability standards: JSON structured logging with key=value fields and never string interpolation, the ERROR/WARN/INFO/DEBUG/TRACE level taxonomy, a /health endpoint with per-component status wired to orchestrator probes, counter/gauge/histogram metric choice with no high-cardinality labels, and correlation-ID propagation across service boundaries. Load when adding logging, metrics, tracing or a health endpoint to a service, or reviewing what a service emits."
    ---
    
    - **Structured logging**: JSON output, `key=value` pairs — never string interpolation in log messages.
    - **Log levels**: ERROR (unrecoverable), WARN (degraded), INFO (state changes), DEBUG (flow), TRACE (off in prod).
    - **Health endpoints**: `/health` with component status, wired to orchestrator probes.
    - **Metrics**: counters for requests, gauges for connections, histograms for latency — no high-cardinality labels.
    - Propagate request/correlation IDs across service boundaries.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related