telemetry-steward

Collect and store FlowDeck telemetry events as append-only JSONL.

20|3|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/DVNghiem/FlowDeck --skill telemetry-steward
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: telemetry-steward
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/telemetry-steward
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill telemetry-steward

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Telemetry Steward captures structured, append-only events from FlowDeck to enable observability, drift diagnosis, and performance validation across sessions.

Core Features & Use Cases

  • Observability: Track context health, agent handoffs, decisions, and readiness metrics over time.
  • Audit & Governance: Provide a traceable signal trail for debugging and governance checks.
  • Use Case: Use this to monitor agent performance and decision quality across long-running workflows.

Quick Start

Enable Telemetry Steward to start writing events to .codebase/TELEMETRY.jsonl and monitor the resulting telemetry signals.

Frequently Asked Questions about telemetry-steward

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

FAQPage Schema
How do I track agent performance and decision quality across long-running workflow sessions?

Telemetry tracking for agent performance captures structured, append-only events during session lifecycles to monitor context health, routing, and decision quality across runs.

What is append-only JSONL telemetry storage and when do I need it for observability?

Append-only JSONL telemetry storage logs immutable event records sequentially, providing a traceable signal trail needed for drift diagnosis, debugging, and governance checks.

How do I start logging observability events to monitor context health and agent handoffs?

Enable telemetry logging to start writing context_action, agent_routing, decision_recorded, and readiness_check events to the .codebase/TELEMETRY.jsonl file for session monitoring.

Can I use telemetry event streams for audit and governance checks in long-running workflows?

Telemetry event streams support audit and governance by providing a structured, traceable signal trail that validates readiness metrics and agent handoffs across long-running workflows.

What are the limitations of using append-only telemetry files for observability?

Append-only telemetry files require retention and aggregation management to prevent unbounded growth, and guardrail guidance is needed to maintain event stream quality over time.