FREE TOOL · NO SIGN-UP · NOTHING YOU PASTE LEAVES YOUR BROWSER
Claude Code skills usage
Which skills does Claude Code actually run for you? One command reads the session logs on your machine and prints each skill it ran, with a count. Paste its output below.
macOS or Linux; on Windows, Git Bash. It reads ~/.claude/projects and prints only skill names and counts.
Your Claude Code skills, most used first
Sample output, not your data. Paste yours to replace it.
Claude Code ran 9 skills 135 times. The three most used took 75% of those runs, and 2 skills ran only once.
No skill runs in that text. Paste the lines the command printed, such as "48 frontend-design".
Skills
9
Runs
135
Top 3 share
75%
Ran once
2
That's one machine. Zest shows it for your whole team: the skills, models and tokens in each engineer's Claude Code sessions, next to the pull requests those sessions led to.
From the transcripts still on the machine: Claude Code deletes them after 30 days unless cleanupPeriodDays says otherwise.
Skill
Runs
Share of runs
frontend-design
48
36%
webapp-testing
31
23%
mcp-builder
22
16%
pdf
14
10%
skill-creator
9
7%
docx
6
4%
xlsx
3
2%
canvas-design
1
under 1%
theme-factory
1
under 1%
Where Claude Code keeps your session logs
Claude Code writes every session to a plain-text transcript, ~/.claude/projects/<project>/<session>.jsonl, and each subagent's to a subagents folder beside it. On Windows, ~/.claude is %USERPROFILE%\.claude. If you set CLAUDE_CONFIG_DIR, the transcripts live under that folder instead, so put its path in the command in place of ~/.claude.
Claude Code deletes transcripts older than cleanupPeriodDays, 30 days by default, so the count covers about your last month of sessions on this machine. Sessions on another laptop, or in the cloud, are not in it.
What the command counts
Claude uses a skill when its description fits the task, or when you invoke it with /skill-name. Each time Claude loads a skill itself, the transcript records a call to its Skill tool with the skill's name, and that call is what the command counts, in your sessions and in your subagents'. A skill you start by typing /skill-name is logged as a slash command, so a skill you only ever type yourself can be missing from the list.
A transcript also holds file contents, command output and anything you pasted, which is why the command prints only its match: grep -o keeps the Skill call, cut keeps the skill's name, and uniq -c counts them. Run it without the last three steps to see exactly what it reads.
From one laptop to your team
The list above is one engineer's machine. Zest is a Claude Code plugin that records each session's skills, models and tokens, redacts secrets on the engineer's machine and collects no code diffs. The dashboard shows them per engineer for the whole team, next to the pull requests the sessions led to, so you can see which skills spread and which sessions ship. Starter is free for 3 seats, no credit card.
TRY IT ON YOUR TEAM
See what your team ships with AI.
Starter is free (3 seats, no credit card). Pro is $49 a month with 5 seats and Max is $149 a month with 10 seats — priced per workspace, not per engineer, with extra seats at $19 a month. See pricing
No. The command runs on your machine and prints only skill names and counts. This page counts what you paste in your browser and sends none of it: not the text, not the skill names, not the totals.
Why is a skill I use missing?+
Usually one of three reasons: its sessions are older than cleanupPeriodDays (30 days by default), so Claude Code has deleted their transcripts; you only start it by typing /skill-name, which is logged as a command rather than a Skill call; or you set CLAUDE_CONFIG_DIR, so your transcripts are not under ~/.claude.
How do I list the Claude Code skills I have installed?+
Personal skills are folders in ~/.claude/skills (run ls ~/.claude/skills), project skills are in .claude/skills inside the repository, and plugin skills come with their plugin. This page answers the next question: which of them Claude Code actually ran.
Can I see this for my whole team?+
Yes, with Zest: a Claude Code plugin that records each session's skills, models and tokens and shows them per engineer, next to the pull requests the sessions led to. Starter is free for 3 seats, no credit card.
