telemetry-observability
CommunityMake your CLI observable.
Authorthiagobutignon
Version1.0.0
Installs0
System Documentation
What problem does it solve?
This Skill addresses the critical lack of structured logging, trace IDs, and persistent telemetry in CLI tools and agents, which hinders effective debugging, MTTR tracking, and performance optimization.
Core Features & Use Cases
- Structured Logging: Ensures all diagnostic output is machine-readable JSON sent to stderr, keeping stdout clean for data.
- Persistent Telemetry: Records every command's event, duration, success status, and metadata in a queryable store (e.g., SQLite).
- Traceability: Implements trace IDs to correlate logs, telemetry, and events across operations.
- Use Case: When a
nooa code writecommand unexpectedly slows down, this skill allows you to quickly query historical telemetry to pinpoint the regression, identify the affected code path via trace IDs, and understand the impact.
Quick Start
Use the telemetry-observability skill to instrument the nooa code write command with structured logging and persistent telemetry.
Dependency Matrix
Required Modules
None requiredComponents
references
💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: telemetry-observability Download link: https://github.com/thiagobutignon/nooa-the-pragmatic/archive/main.zip#telemetry-observability Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.