Telemetry Inspect

What it does

Telemetry Inspect provides a one-shot, read-only health check for an OrchestKit project's telemetry pipeline. It enumerates known telemetry and log files, reports recent write activity, file sizes and line counts, schema-lock coverage (which files have validators), orphaned files on disk, and simple growth trend metrics. The output can be a human-friendly ASCII report or structured JSON for tooling.

When to use it

• Before or after risky refactors to confirm telemetry still writes as expected.
• As a weekly health check on long-running projects.
• When higher-level analytics look suspicious and you need to inspect the raw files.
• After adding a new telemetry writer to confirm it appears in the registry.
• For audits comparing schema-locked files vs. drift-vulnerable files.

What's included

• Scripts: none bundled in the skill directory, but the skill references a references/telemetry-inventory.md and lib/telemetry-schemas.ts in the repo.
• References: inventory of telemetry paths and schema lock definitions.
• Instructions: deterministic steps to glob telemetry files, read limited samples, stat for size/mtime, classify health (warn/critical), detect orphans, and render ASCII or JSON output.

Compatible agents

Designed for Claude Code execution environments (agent-run tools that support Bash, Read, Glob). The skill lists allowed tools such as Bash and Read and is straightforward to run from an LLM-enabled agent invocation.