Observability
Skill kimtth/agent-skill-100-lines-or-less/skills/observability
Use when: instrument a system with logs, metrics, and traces to understand it in production.From its SKILL.md
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill observabilityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 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.
SKILL.md
1.1 KB, 210 tokens by cl100k_base, as published. Nobody here has run it
Goal: be able to answer new questions about production without redeploying.
Use for:
- instrumenting services for debugging and alerting
- diagnosing latency, errors, and saturation
- designing what to measure and emit
Workflow:
- Cover the three pillars: logs, metrics, and traces.
- Emit structured logs with correlation/trace IDs.
- Track the golden signals: latency, traffic, errors, saturation.
- Propagate trace context across service boundaries.
- Alert on symptoms users feel, not noisy internals.
- Verify you can trace one request end to end.
What to capture:
- request-level traces with timing per span
- RED/USE metrics for services and resources
- structured, queryable logs with context
- meaningful, low-noise alerts on SLOs
Rules:
- correlate logs, metrics, and traces with shared IDs
- alert on user-facing symptoms, not every blip
- instrument boundaries and dependencies first
- never log secrets or PII in telemetry
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.