logging-observability-skill

logging-observability-skill is a skill for OpenCode from darellchua2/opencode-config-template. It costs 30 tokens per session (2,824 once invoked), scanned A, original, Apache-2.0.

A guide to structured application logs, distributed tracing, metrics, and error monitoring. Observability means collecting information that helps you understand what software is doing in development and production.

In plain words
What is it for?
It covers JSON logging, OpenTelemetry tracing and metrics, Sentry error tracking, correlation IDs, log levels, and monitoring stacks such as Grafana and Jaeger.
Why use it?
It helps developers find failures and follow requests across services instead of relying on scattered, hard-to-search log messages.

Skill for OpenCode

Written for OpenCode: installed under .opencode/. Also seen: mentions OpenCode.

Good fit It covers JSON logging, OpenTelemetry tracing and metrics, Sentry error tracking, correlation IDs, log levels, and monitoring stacks such as Grafana and Jaeger.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/darellchua2/opencode-config-template/logging-observability-skill
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add darellchua2/opencode-config-template --skill logging-observability-skill
Clone the repo
git clone --depth 1 https://github.com/darellchua2/opencode-config-template

Made for: OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for logging-observability-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/logging-observability-skill.svg)](https://agentmods.dev/skills/darellchua2/opencode-config-template/logging-observability-skill)
Your own site
<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/logging-observability-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/logging-observability-skill.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,824 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.02824
Opus 5 $0.00015 $0.01412
Sonnet 5 $0.00006 $0.00565
Haiku 4.5 $0.00003 $0.00282

Measured 4d ago against content hash 55d8207b033b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

logging-observability-skill scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

opencode_app/.opencode/skills/logging-observability-skill/SKILL.md · 410 lines

How it starts

The opening of the file, as written. The whole thing — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.

What I do

I help you implement comprehensive logging and observability:

  1. Structured Logging: JSON logging with Winston, pino, and structlog
  2. OpenTelemetry: Distributed tracing and metrics instrumentation
  3. Error Monitoring: Sentry integration patterns for error tracking
  4. Correlation IDs: Request tracing across services
  5. Log Levels: Proper level usage and filtering strategies
  6. Observability Stack: Setup guidance for ELK, Grafana, Jaeger

When to use me

Use this skill when:

  • Setting up structured logging in a new project
  • Integrating OpenTelemetry for distributed tracing
  • Configuring Sentry for error monitoring
  • Implementing correlation IDs for request tracing
  • Designing log aggregation architecture
  • Choosing between logging libraries (Winston vs pino, structlog vs logging)
  • Setting up log levels and filtering
  • Creating observability dashboards and alerts
  • error-resolver-workflow-skill: Handles runtime error diagnosis. This skill handles instrumentation setup (Sentry integration, structured logging configuration). Error-resolver consumes the data this skill produces.
  • docker-containerization-skill: Container log driver configuration.
  • performance-optimization-skill: Uses tracing data for performance analysis.

Step 1: Structured Logging

Node.js (pino - Recommended for performance)

import pino from "pino"

const logger = pino({
  level: process.env.LOG_LEVEL || "info",
  transport:
    process.env.NODE_ENV === "development"
      ? { target: "pino-pretty", options: { colorize: true } }
      : undefined,
  formatters: {
    level: (label) => ({ level: label }),
  },
  defaultMeta: {
    service: "my-api",
    version: process.env.APP_VERSION || "1.0.0",
  },
})

export default logger

Node.js (Winston - More configurable)

import winston from "winston"

const logger = winston.createLogger({
  level: process.env.LOG_LEVEL || "info",
  format: winston.format.combine(
    winston.format.timestamp(),
    winston.format.errors({ stack: true }),
    winston.format.json()
  ),
  defaultMeta: { service: "my-api" },
  transports: [
    new winston.transports.Console(),
    new winston.transports.File({ filename: "logs/error.log", level: "error" }),
  ],
})

if (process.env.NODE_ENV !== "production") {
  logger.add(
    new winston.transports.Console({
      format: winston.format.combine(winston.format.colorize(), winston.format.simple()),
    })
  )
}

Read the full file on GitHub · 410 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 410 lines · 30 tokens per session scan A 55d8207b033b

Subscribe to this mod's changes

logging-observability-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 30 tokens to every session and 2,824 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens