install-skill-tracker_skill

Overview

This skill installs a global Claude Code skill tracking system that logs every skill invocation across all projects. It captures execution start/end, duration, token usage, and the user prompt that triggered each skill for centralized analysis. Use it to surface costly or slow workflows and to discover opportunities for new automated skills.

How this skill works

The installer creates a ~/.claude/ directory structure and places hook scripts that run on UserPromptSubmit, PreToolUse, and PostToolUse events. Hooks write compact JSONL entries to ~/.claude/activity-logs/ (prompts.jsonl and skill-usage.jsonl) containing timestamps, session IDs, project paths, token metrics, and durations. Included analysis scripts parse those logs to produce frequency, timing, token-cost, and cache-efficiency reports.

When to use it

• Set up centralized tracking across all Claude Code projects.
• Measure skill execution time to find slow or expensive steps.
• Monitor token usage and estimate API costs per skill.
• Identify repeated prompts or workflows for new skill creation.
• Audit prompt cache effectiveness and optimization opportunities.

Best practices

• Install globally in ~/.claude/ so logs aggregate across projects.
• Merge hook entries into an existing ~/.claude/settings.json instead of overwriting.
• Make hook and analysis scripts executable (chmod +x).
• Verify timing by running a sample skill and checking skill-usage.jsonl.
• Keep logs local and rotate or delete activity-logs periodically for privacy or disk management.

Example use cases

• Find which skills consume the most tokens and estimate monthly API spend.
• Discover long-running skills to prioritize for optimization or parallelization.
• Surface repeated manual prompts that can be turned into new, reusable skills.
• Compare session activity timelines to identify distraction gaps or workflow bottlenecks.
• Validate prompt cache behavior by measuring cache read vs creation tokens.