​

Skill usage

Atlan derives skill usage from traces. When an agent runs, the trace records the skills involved. Atlan matches those records to the skill’s content fingerprint and automatically adds the run to its Usage tab. You do not need to record a separate usage event. When trace data contains the information needed for attribution, Atlan can use it to show run volume, success and latency metrics, token use, people, agents, versions, and the trace list.

​

Match confidence

Each trace explains how it was attributed:

• Exact match: The content digest matches an exact skill version.
• SKILL.md match: The entrypoint matches, but supporting files may differ.
• Name match: The trace identified the skill by name when stronger content evidence was unavailable.

Use exact matches for version-level analysis. Treat weaker matches as useful evidence with more uncertainty.

​

Read usage carefully

Treat usage as evidence, not a quality verdict. A high run count can show reuse; it does not by itself show that the result was correct. Prefer an exact match when you need version-level analysis, and follow the linked trace only when you have permission to inspect it.