> For the complete documentation index, see llms.txt.
Skip to main content

Check out Port for yourself ➜ 

Skills usage

Organizations adopting Claude Skills can't answer the questions that matter. Are people using skills at all, or did they try once and stop? Are the same skills coming back day after day, or is everyone building throwaway experiments? Is the knowledge staying locked to individuals, or becoming shared across teams? Without visibility, skill investment decisions get made on anecdote rather than usage data.

What to track

  • Skill invocations and skills used: Total invocation volume alongside how many distinct skills are active, to separate breadth of adoption from depth.
  • Avg. invocations per active skill: Whether usage is deepening on skills people already have, or only ever spreading to new ones.
  • Usage by sharing scope: Whether invocations are staying personal or becoming reusable across a team.
  • Days active per skill: How many separate days a skill was used, to distinguish habitual tools from one-off experiments.
  • Spend concentration: Where skill-related consumption is concentrated, so cost outliers are visible.

How Port helps

Port ingests skill usage data through the Claude integration and models it in your context lake alongside the rest of your engineering context. This means adoption, depth, and reuse metrics for skills sit next to the same dashboards you already use for AI tool adoption, rather than in a separate reporting surface. Skills that prove themselves can then be promoted into the Port Skill Registry for centralized discovery and management.

Example scenario

A platform team wants to know if the Skills they've built for Claude Code are actually catching on. Port's dashboard shows invocations rising while the number of distinct skills used stays flat, indicating people are going deeper on a handful of proven skills rather than experimenting broadly. The sharing-scope breakdown shows most of that usage is still personal. The team uses this to identify which personal skills are used consistently enough to promote into shared, project-level skills.

Example dashboard

Claude Skills Adoption & Usage dashboard showing invocation trends, sharing scope breakdowns, and the most consistently used skills

Example dashboard based on Visualize Claude Skills adoption and usage guide.

Implement this use case

Follow the recommended guides below to implement this use case.