observability

Name: observability
Availability: InStock
Author: WrongStack

Instrument WrongStack applications with structured logs, traces, and metrics.

224|27|Updated May 12, 2026

Search Tags:#security #logging #metrics #observability #tracing #opentelemetry #redaction

Ready to run

npx skills add https://github.com/WrongStack/WrongStack --skill observability-wrongstack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: observability
Source: https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/observability
Command: npx skills add https://github.com/WrongStack/WrongStack --skill observability-wrongstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Instrument WrongStack applications with structured logs, traces, and metrics to enable end-to-end observability and governance.

Core Features & Use Cases

Structured logging: emit JSON to stdout with traceId and contextual fields to enable search and correlation.
Tracing and metrics: instrument tool calls and operations with spans, timing, and latency tracking for performance visibility.
Guardrails: redact secrets, protect PII, and ensure consistent observability across components and environments.

Quick Start

Configure your application to emit structured JSON logs with a traceId for end-to-end correlation.

Frequently Asked Questions about observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I instrument structured logs with traceId for end-to-end correlation?▼

Structured logging with traceId emits JSON to stdout with contextual fields to enable search and correlation. It enforces traceId usage across components and environments to link events, tool calls, and user actions consistently.

How do I trace tool calls and measure latency using OpenTelemetry patterns?▼

Tracing tool calls with OpenTelemetry-like patterns instruments operations with spans and timing. This measures latency and tracks performance visibility by recording execution timing for events and tool calls across development and production environments.

How do I redact secrets and protect PII in application observability data?▼

Observability guardrails redact secrets and protect PII to ensure consistent governance across components. This prevents sensitive data from leaking into structured logs, traces, and metrics while maintaining performance visibility.

Can I use this observability instrumentation across both development and production environments?▼

Yes, observability instrumentation applies across development and production environments. It ensures consistent logging, tracing, and metrics collection for events, tool calls, and user actions regardless of the deployment context.

What is the best way to enable end-to-end observability for application events and user actions?▼

End-to-end observability is enabled by instrumenting applications with structured logs, traces, and metrics. This approach enforces traceId usage, redacts secrets, and adheres to OpenTelemetry-like patterns for spans and timing to capture events and user actions.