install-skill-tracker

Install global Claude Code hooks to log skill usage and token metrics.

90|12|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/dmccreary/claude-skills --skill install-skill-tracker-dmccreary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: install-skill-tracker
Source: https://github.com/dmccreary/claude-skills/tree/main/skills/archived/install-skill-tracker
Command: npx skills add https://github.com/dmccreary/claude-skills --skill install-skill-tracker-dmccreary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) and references (resource) components.

What problem does it solve?

This Skill installs a global Claude Code skill-tracking system using hooks to log prompts, invocations, durations, and token usage across all projects.

Core Features & Use Cases

  • Global prompts and skill invocation logging
  • Duration, token usage, and session correlation
  • Centralized analytics for optimization

Quick Start

Install the global tracker in ~/.claude and verify logs with the provided scripts.

Frequently Asked Questions about install-skill-tracker

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

FAQPage Schema
How do I track Claude Code skill usage across all my projects?▼

Install the global skill tracker in ~/.claude to automatically log skill invocations, prompts, execution duration, and token usage across all Claude Code projects. The system uses hooks to capture metrics in prompts.jsonl and skill-usage.jsonl files for centralized monitoring.

What metrics does global skill tracking capture?▼

The tracker logs prompts, skill start and end events, execution duration, token consumption, and session identifiers. These metrics flow into centralized analytics files enabling cross-project pattern analysis, cost tracking, and optimization opportunity identification.

How do I set up and verify the skill tracking system?▼

Run the installation steps provided in the Skill to deploy hooks under ~/.claude. Verify logs are generating by checking prompts.jsonl and skill-usage.jsonl, then use the included analysis scripts to review tracked metrics and confirm proper hook integration.

Can I use skill tracking to analyze patterns across multiple projects?▼

Yes. The global hooks capture skill usage uniformly across all Claude Code projects, enabling cross-project pattern analysis. Aggregated logs support identifying automation opportunities, cost trends, and prompt effectiveness across your entire workflow.

What's the best way to monitor token usage and project costs?▼

The skill tracker logs token metrics per invocation with session correlation, centralizing cost data in skill-usage.jsonl. Use the included analysis scripts to aggregate token consumption across projects and identify high-cost skills for optimization.