logging

Emit structured JSONL logs with thread_id and run_id context.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/wlee075/chatbot --skill logging-wlee075
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: logging
Source: https://github.com/wlee075/chatbot/tree/main/skills/logging
Command: npx skills add https://github.com/wlee075/chatbot --skill logging-wlee075

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a consistent, session-scoped logging layer that emits structured JSONL events with a common set of context fields, enabling reliable observability, debugging, and auditing across AI workflow nodes.

Core Features & Use Cases

  • Structured JSONL log lines with standard fields: thread_id, run_id, node_name, section_name, section_index, iteration, plus flat extra fields per event.
  • Event-type inventory supports node_start, node_end, and various node-specific events, with optional DEBUG gating for verbose prompts and responses.
  • Centralized per-session log files (and per-thread/session separation) for traceability and post-hoc analysis.

Quick Start

Start emitting logs by calling log_event() with the standard context for each operation in your code.

Frequently Asked Questions about logging

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

FAQPage Schema
How do I implement structured JSONL logging for AI session observability?▼

Structured JSONL logging for AI session observability is implemented by emitting log events with standard context fields like thread_id, run_id, and node_name. This enforces per-event schemas and flat extra-field merges for reliable debugging.

What is the best way to debug AI workflow nodes using session-scoped logs?▼

Session-scoped logging provides centralized per-session and per-thread log file separation for AI workflow nodes. This enables reliable post-hoc analysis and auditing by tracing specific thread_id and run_id context throughout the execution flow.

Does this structured logging approach support standard context fields for Python debugging?▼

This structured logging approach supports Python debugging by enforcing standard context fields including node_name, section_name, section_index, and iteration. It emits structured JSONL lines with flat extra fields per event for comprehensive observability.

Can I gate verbose prompt and response logs behind a DEBUG level for monitoring?▼

You can gate verbose prompt and response logs behind an optional DEBUG level for monitoring. The event-type inventory supports node_start, node_end, and node-specific events, allowing controlled verbosity during AI session observability and auditing.

When do I need per-thread log file separation for AI observability?▼

Per-thread log file separation for AI observability is needed when debugging concurrent AI workflow nodes requiring distinct thread_id and run_id context. It ensures centralized traceability and reliable post-hoc analysis across multiple session scopes.