Agent skill · data analytics · yonatangross
telemetry-inspect
Read-only check of this project's OrchestKit telemetry files: write counts, sizes, schema locks, growth and orphans. Use when verifying the observability pipeline or hunting a missing writer.
Why this skill is useful
Adds specific commands and checks for monitoring the OrchestKit telemetry pipeline that the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-08-06. 215 stars on the source repository.
What this skill does
telemetry-inspect One-shot health check for OrchestKit's telemetry pipeline. Reports writer activity, file sizes, schema lock coverage, orphan files, and growth warnings. Use when verifying the pipeline is flowing correctly or debugging a missing writer. When to use Before or after a risky hook refactor, to prove telemetry still writes as expected Weekly health check on a long-running project When analytics output looks suspicious — inspect the underlying data first When adding a new telemetry file and wanting to confirm it's picked up Auditing which files are schema-locked vs. drift-vulnerable What it checks 1. Writer activity — for each registered telemetry file, recent write count (from mtime scan) and last-write delta 2. File health — size (warn at 256 KB, critical at 1 MB), line count, mtime 3. Schema lock status — which files have validators in lib/telemetry-schemas.ts 4. Orphan detection — files on disk under .claude/{telemetry,logs,state,feedback}/ that aren't in the registry (possible stale writer or new file needing schema), plus inventory rows whose writer hook no longer exists in src/hooks/src/ (dead writer → orphan) 5. Growth trend — bytes per hour since session start (fire alert if > 100 KB/hr) 6. Coordination layer (M168) — live counts from sessions.db (running sessions, held locks, pending worktree links, skill invocations) plus write throughput from coordination-metrics.jsonl 7. Runtime fired-census — which hooks actually fired, from the per-invocation records run-hook.mjs writes to ~/.claude/analytics/hook-timing.jsonl. Checks 1–4 answer "is the file being written?"; this answers "is the writer running at all?" — the upstream question. A hook can be wired and reachable (the closure gate proves that statically) and still never fire: #2886 shipped exactly that with 12 green tests. Usage Default mode: terminal-friendly ASCII report. --json emits a structured result suitable for piping into another tool or uploading. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills yonatangross/telemetry-inspect--544ae8