skill-stats

Analyze Claude Code transcript JSONL files to compute Skill invocation and trigger hit-rate statistics.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/devbasex/ai-plugins --skill skill-stats-devbasex
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: skill-stats
Source: https://github.com/devbasex/ai-plugins/tree/main/plugins/ndf/skills/skill-stats
Command: npx skills add https://github.com/devbasex/ai-plugins --skill skill-stats-devbasex

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes scripts (resource) components.

What problem does it solve? It is hard to know which Skills are actually being used, which ones fire automatically when they should, and which descriptions or trigger keywords need improvement. This Skill parses Claude Code transcript logs and turns them into concrete usage statistics. ## Core Features & Use Cases - Invocation Counting: Separately counts automatic (model-invoked) and explicit (slash command) Skill activations per Skill. - Trigger Hit-Rate Analysis: Matches user messages against declared trigger keywords and measures how often the matching Skill auto-fires afterward. - Flexible Filtering: Filter by date range, Skill name, or project, with per-project breakdowns and Markdown or JSON output. - Use Case: Run a 90-day audit across all projects to find Skills with low hit rates, then rewrite their descriptions or trigger keywords to improve automatic activation. ## Quick Start Ask the assistant to run the skill-stats analysis over the last 90 days of Claude Code transcripts and show the per-Skill hit-rate table.

Frequently Asked Questions about skill-stats

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

FAQPage Schema
How do I measure Claude Code Skill usage statistics?โ–ผ

Run the skill-stats script, which scans ~/.claude/projects/*.jsonl transcripts and counts automatic Skill tool invocations plus explicit slash-command calls per Skill. Results are shown as a Markdown table or JSON with per-project breakdowns.

How is the Skill trigger hit rate calculated?โ–ผ

Trigger keywords are extracted from the full-width parenthesized list at the end of each Skill's description or when_to_use field. A hit is counted when a user message containing a trigger keyword is followed by an automatic invocation of that Skill before the next user turn.

Can I filter Skill statistics by date range or project?โ–ผ

Yes. Use --days, --from, and --to for date filtering, --project for project name matching, and --by-project to output a separate table per project. The default window is the last 90 days.

Why does a Skill show zero triggers or no hit rate?โ–ผ

Skills without declared trigger keywords in their description or when_to_use fields cannot have related-topic counts, so hit rate is not computed. Workflow Skills invoked only via slash commands typically fall into this category.

What are the requirements to run the transcript analysis script?โ–ผ

You need Python 3.8 or later with only the standard library, and transcript JSONL files present under ~/.claude/projects. Transcript retention depends on the cleanupPeriodDays setting, which the NDF plugin keeps at 90 days.