telemetry

Name: telemetry
Availability: InStock
Author: ai-sand-castles

Log structured agent team orchestration events to per-session files.

Updated Aug 27, 2026

Search Tags:#logging #observability #telemetry #non-blocking #log-rotation #team-orchestration

Ready to run

npx skills add https://github.com/ai-sand-castles/local-marketplace --skill telemetry-ai-sand-castles

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: telemetry
Source: https://github.com/ai-sand-castles/local-marketplace/tree/main/test-automation-plugin/skills/telemetry
Command: npx skills add https://github.com/ai-sand-castles/local-marketplace --skill telemetry-ai-sand-castles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Telemetry for agent team orchestration, providing structured, non-blocking logs to improve observability and reliability.

Core Features & Use Cases

Non-blocking, append-only event logging across lifecycle, coordination, progress, test, and resource events
Opt-in configuration via team definitions, environment variables, or config files
Session-based log files with 10MB rotation to keep logs manageable
Real-time, timestamped, pipe-delimited event formats for easy parsing

Quick Start

Log a sample lifecycle event after spawning an agent to verify the telemetry pipeline.

Frequently Asked Questions about telemetry

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

FAQPage Schema

How do I add non-blocking logging for agent team orchestration?▼

Non-blocking logging for agent team orchestration is handled by appending structured, timestamped events to per-session log files. It catches all errors and returns a success status, guaranteeing execution never halts during writes.

What types of structured telemetry events can I log for multi-agent coordination?▼

Telemetry for multi-agent coordination supports five structured event types: lifecycle, coordination, progress, test, and resource. Each event is logged with a real-time timestamp in a pipe-delimited format for easy parsing.

How does log rotation work for long-running observability sessions?▼

Log rotation for long-running observability sessions triggers automatically when a per-session log file reaches 10MB. This keeps telemetry logs manageable without manual intervention or blocking the orchestration process.

Can I configure telemetry logging through environment variables or config files?▼

Yes, telemetry logging is opt-in and can be configured through team definitions, environment variables, or config files. This allows you to enable structured event tracking without modifying core orchestration logic.

Why does my telemetry logging never throw exceptions or halt agent execution?▼

Telemetry logging never throws exceptions because it guarantees non-throwing behavior by catching all errors internally and returning a success status. This ensures your agent team orchestration execution never halts due to logging failures.

Is non-blocking telemetry logging suitable for high-scale multi-agent systems?▼

Non-blocking telemetry logging is suitable for high-scale multi-agent systems because it uses append-only writes and automatic 10MB log rotation. This prevents I/O bottlenecks and keeps logs manageable during long-running sessions.