Install and set up the OpenClaw Skill Usage plugin. Use when users say: - "install skill usage" - "setup skill usage" - "add skill usage analytics" - "instal...
Install and configure the OpenClaw Skill Usage plugin.
This skill performs three kinds of actions as part of its normal purpose:
openclaw-skill-usage)Use it only when the user explicitly wants skill-usage analytics and understands the local-vs-cloud tradeoff.
After setup, users can:
1d, 7d, 30d, and allUse this skill when the user expresses intent to install, enable, or configure skill usage analytics.
Common triggers include:
Use this skill when the user wants to:
openclaw-skill-usage plugin/skillusage commandsskill_usage_stats tool from agentstop or statusThis skill is especially appropriate when the user is still in the setup / enablement / verification phase and has not yet fully established the plugin on their machine.
Do not use this skill for:
This setup installs the npm package:
openclaw plugins install openclaw-skill-usage
This provides:
/skillusage slash commandsskill_usage_stats toolSource repository:
By default, the plugin is useful locally and can still answer top / status with local-only data.
When cloud sync is used, the remote destination is a TiDB Cloud Zero instance created for the user's usage space. The plugin's /skillusage status output shows the cloud instance id and a claim URL for that instance.
That claim URL matters: the user can use it to claim the TiDB Cloud Zero instance into their own TiDB Cloud account, making the backend directly visible and controllable from their side rather than remaining an opaque shared service.
Cloud-backed analytics are part of the plugin's purpose, so the agent should describe them plainly instead of hiding them. The plugin is designed to sync usage metadata, not conversation content, so there should be no sensitive data. The intended synced fields are limited to:
The plugin does not sync:
This task is not complete until all of the following are true:
/skillusage status works/skillusage top 7d works/skillusage join-token and /skillusage join <token>Run:
openclaw plugins install openclaw-skill-usage
If the user is working from a local cloned repo instead of npm, a development install may use:
openclaw plugins install --link
But prefer the published npm package for normal setup.
Run:
openclaw gateway restart
Before restarting, tell the user clearly that the gateway will restart and they may need to wait about a minute before testing commands.
Check:
/skillusage status
/skillusage top 7d
A successful install should return usable output rather than a missing-command or plugin-load error.
Compact top output:
skill: weather (37)
- agent: elon 26 | main 10 | tim 1
- channel: disc/el 26 | wa 6 | tim 2 | unknown 3
=====================================
skill: skill-vetter (12)
- agent: main 9 | tim 2 | elon 1
- channel: wa 7 | disc/el 3 | tim 1 | unknown 1
=====================================
skill: github (8)
- agent: elon 6 | main 1 | unknown 1
- channel: disc/el 6 | wa 1 | unknown 1
Status output:
Skill usage status:
data source: cloud-synced usage space
scope: current usage space
usage space: 7f2c... (joined)
this installation: Mac-mini
database: openclaw_skill_usage
cloud instance: zero_abc123
expires at: 2026-04-06T10:00:00.000Z
claim URL: https://...
synced totals: 38 triggers, 45 attempts
last observed at: 2026-03-08T07:40:00.000Z
last cloud sync: 2026-03-08T07:40:02.000Z
pending local records: 0
last sync error: none
metadata sent: skill id/name, installation id/label, channel account key/label/platform, agent id, routing/session identifiers, timestamps, status, latency
By default, one installation starts in its own local usage space.
Only proceed with shared usage-space setup if the user explicitly wants cross-machine sharing and understands that usage metadata will be written to the TiDB Cloud Zero instance for that usage space.
If the user wants to share usage across multiple installations:
/skillusage join-token
/skillusage join <token>
After join, top can show multiple installation blocks in one shared leaderboard.
"Install skill usage"
openclaw-skill-usage/skillusage status"Check if skill usage is working"
/skillusage status/skillusage top 7d"Show my top skills"
/skillusage top 7d or use skill_usage_stats"Set up a shared leaderboard across two machines"
/skillusage join-token on machine 1/skillusage join <token> on machine 2/skillusage status and /skillusage top 7d"Enable /skillusage"
status and topZIP package — ready to use