skills.rest
LayerDynamics
LayerDynamicsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

cc-telemetry

Query Claude Code telemetry for tool call history, session stats, and error rates.

Updated Feb 25, 2026
Search Tags:#debugging#monitoring#claude code#telemetry#tool usage#plugin issues
One-click install
npx skills add https://github.com/LayerDynamics/Lore --skill cc-telemetry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cc-telemetry
Source: https://github.com/LayerDynamics/Lore/tree/main/lore/extensions/cc-telemetry/skills/cc-telemetry
Command: npx skills add https://github.com/LayerDynamics/Lore --skill cc-telemetry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill allows users to query and understand the telemetry data generated by the cc-telemetry daemon, which monitors tool calls, session statistics, and events within Claude Code.

Core Features & Use Cases

  • Real-time Monitoring: View live tool call history, session stats, error rates, hook events, and timing data.
  • Debugging: Troubleshoot plugin issues by examining detailed telemetry.
  • Usage Analysis: Understand patterns in tool usage and agent behavior.
  • Auditing: Verify which tools Claude has invoked.

Quick Start

Query the cc-telemetry daemon for live tool call data.

Frequently Asked Questions about cc-telemetry

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

FAQPage Schema
How do I monitor Claude Code tool call history in real-time?▼

Claude Code telemetry data is queried through the cc-telemetry daemon, which records real-time tool call history, session statistics, hook events, and timing information. You retrieve this data by executing the cc-telemetry Python script with specified arguments.

Can I debug Claude Code plugin issues by examining tool invocation logs?▼

You can debug Claude Code plugin issues by querying the cc-telemetry daemon to examine detailed tool invocation logs, error rates, and hook events. This exposes exactly which tools were called and where failures occurred during a session.

How do I audit which tools Claude has invoked during a session?▼

You audit invoked tools by querying Claude Code telemetry data, which records detailed tool call history and session statistics. Running the cc-telemetry Python script retrieves this invocation history for verification.

What is the best way to analyze Claude Code usage patterns and agent behavior?▼

The best way to analyze Claude Code usage patterns is by querying the cc-telemetry daemon for session statistics and timing information. This telemetry data reveals behavioral trends and tool usage frequencies across your interactions.

Does querying telemetry require a specific environment or dependencies?▼

Querying telemetry requires an environment capable of executing the cc-telemetry Python script. The Skill lists no external dependencies, but the cc-telemetry daemon must be actively running to capture and serve the tool call data.

Related Skills

Explore More Software Engineering Skills→
jabberlockiejabberlockie

log

Parse JSONL session transcripts and generate SQL for Supabase upload.

Community
Advanced
liaoxinjie666liaoxinjie666
4

guide-monitoring

Inspect and export usage stats, request logs, and runtime system logs for proxies.

Community
Basic
taloncjonestaloncjones

claude-code-platform-reference

Document Claude Code configuration resolution, plugin installation, and hook registration.

Community
Advanced
ByronWilliamsCPAByronWilliamsCPA

usage-report

Track Claude Code token usage across local JSONL transcripts.

Official
Advanced