Usage Analytics

This guide covers tracking how agents use your skills locally.

Why analytics?

Understanding usage helps you:

Identify which sections agents read most
Find content that’s never accessed (candidates for removal)
Optimize skill structure based on real patterns

How it works

When you use gateway commands (skc show, skc open, skc search), skillc logs each access:

Timestamp
Command used
Skill and section accessed
Working directory context

Logs are stored locally in .skillc-meta/logs.db within each skill’s runtime directory.

View statistics

skc stats my-skill

Example output:

my-skill usage statistics (last 30 days)

Total accesses: 47
Unique sections: 12

Top sections:
  1. Installation (15 accesses)
  2. Troubleshooting (12 accesses)
  3. API Reference (8 accesses)

Unused sections:
  - Contributing
  - Changelog

Access by command:
  show: 35
  search: 8
  open: 4

Filter by time

skc stats my-skill --since 7d    # Last 7 days
skc stats my-skill --since 30d   # Last 30 days
skc stats my-skill --since 2024-01-01

JSON output

For programmatic analysis:

skc stats my-skill --format json

{
  "skill": "my-skill",
  "period": {
    "start": "2024-01-01T00:00:00Z",
    "end": "2024-01-30T23:59:59Z"
  },
  "total_accesses": 47,
  "sections": [
    { "name": "Installation", "count": 15 },
    { "name": "Troubleshooting", "count": 12 }
  ]
}