telemetry-analysis

Analyze local YAMTAM telemetry logs for hook activity, token usage, and trust health.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/hbvg234/jnmt.vn --skill telemetry-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: telemetry-analysis
Source: https://github.com/hbvg234/jnmt.vn/tree/main/.claude/skills/telemetry-analysis
Command: npx skills add https://github.com/hbvg234/jnmt.vn --skill telemetry-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Telemetry analysis helps teams quickly interpret local telemetry data to understand system health, hook activity, and resource usage without external services.

Core Features & Use Cases

  • Inspect hook firing patterns, token usage, and decision outcomes from local logs.
  • Assess trust health, detect anomalies, and plan mitigations for potential issues in agent behavior.
  • Use in engineering, security reviews, and product-monitoring conversations to generate concise telemetry reports.

Quick Start

Run the telemetry-analysis skill after YAMTAM has collected data in .claude/state and session logs to obtain an immediate health overview.

Frequently Asked Questions about telemetry-analysis

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

FAQPage Schema
How do I analyze local telemetry data and audit logs for hook activity?

You can analyze local telemetry data by running the telemetry-analysis skill to interpret audit-chain logs and telemetry.jsonl files. This surfaces hook firing patterns, token usage, and decision outcomes without requiring external services.

How do I assess agent trust health and detect anomalies from session logs?

Assess trust health by interpreting session-trust.json and session-read-log.txt files. The analysis detects anomalies in agent behavior and evaluates bypass usage to help plan mitigations for potential issues.

Can I generate operational telemetry reports for security reviews without external services?

Yes, telemetry analysis generates concise operational reports for security reviews by interpreting local .claude/state/ logs. It delivers deterministic health metrics and expensive-operation insights entirely offline.

What's the best way to surface token usage and bypass metrics from YAMTAM telemetry?

Surface token usage and bypass metrics by running telemetry-analysis after YAMTAM has collected data in .claude/state. It interprets telemetry.jsonl and audit-chain.log to produce a compact operational view.

Do I need YAMTAM to collect data before analyzing project telemetry health?

Yes, YAMTAM must first collect data in .claude/state and session logs. The skill interprets these generated files to provide an immediate health overview for engineers and product owners.

What limitations exist when interpreting local audit-chain logs for system health?

Interpreting local audit-chain logs relies entirely on the data YAMTAM collected in .claude/state. The analysis is limited to deterministic metrics from existing local log files and does not query external services.