How do I install the Clawmetry Selfcheck skill?

Run npx skillmds add vivekchand/clawmetry-selfcheck in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Clawmetry Selfcheck safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Clawmetry Selfcheck?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Clawmetry Selfcheck free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Clawmetry Selfcheck?

vivekchand (@vivekchand) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Clawmetry Selfcheck by vivekchand — Agent Skill

Name: Clawmetry Selfcheck
Rating: 4.666666666666667 (3 reviews)
Author: vivekchand

Clawmetry Selfcheck

Read your own agent telemetry from ClawMetry (waste, progress, cost) and act on it before finishing a task. Use when ClawMetry is installed on this machine and you want to check whether you are re-reading files, spinning in loops, or burning budget.

vivekchand 0035a5a 2.1 KB Updated Sep 9, 2026

File contents

ClawMetry self-check

ClawMetry observes AI agent sessions on this machine (read-only). Use its CLI to see your own telemetry and improve your behaviour mid-task.

All commands are read-only, exit 3 when ClawMetry has no data source running (safe to skip silently), and support --json.

The 3-step check (run before finishing a task)

# 1. Re-read tax: files you paid to read more than once
clawmetry waste --since 6h --json

# 2. Spinning check: forward progress + loop signals
clawmetry progress --json

# 3. Spend check
clawmetry usage --json

How to act on what you find

Signal	Action
A file with `reads > 3` in `waste`	Stop re-reading it. Write its structure into your working notes once; use offset-ranged reads for big files.
High `ratio` (tokens per state-delta) in `progress`	You are burning tokens without producing new state. Write down what you tried, change strategy.
`loop_signals` non-empty	You repeated near-identical calls. Do not retry the same thing; diagnose instead.
Cost spike in `usage`	Check `usage --by model`: are you using a bigger model than the task needs?

Digging deeper

clawmetry sessions --active                  # who is running
clawmetry sessions <SID> --transcript        # what actually happened
clawmetry sessions <SID> --cost              # where the money went (incl. sub-agents)
clawmetry sessions <SID> --errors            # error events only
clawmetry activity --follow --max-events 50  # live NDJSON event stream
clawmetry usage --efficiency                 # A-F efficiency grade

Exit codes: 0 ok, 3 no data source (skip), 4 feature needs an upgrade (stderr carries a JSON body with upgrade_url; surface it to your human).

---name: clawmetry-selfcheckdescription: Read your own agent telemetry from ClawMetry (waste, progress, cost) and act on it before finishing a task. Use when ClawMetry is installed on this machine and you want to check whether you are re-reading files, spinning in loops, or burning budget.--- # ClawMetry self-check ClawMetry observes AI agent sessions on this machine (read-only). Use its CLI to see your own telemetry and improve your behaviour mid-task. All commands are read-only, exit `3` when ClawMetry has no data source running (safe to skip silently), and support `--json`. ## The 3-step check (run before finishing a task) ```bash # 1. Re-read tax: files you paid to read more than once clawmetry waste --since 6h --json # 2. Spinning check: forward progress + loop signals clawmetry progress --json # 3. Spend check clawmetry usage --json ``` ## How to act on what you find | Signal | Action | |---|---| | A file with `reads > 3` in `waste` | Stop re-reading it. Write its structure into your working notes once; use offset-ranged reads for big files. | | High `ratio` (tokens per state-delta) in `progress` | You are burning tokens without producing new state. Write down what you tried, change strategy. | | `loop_signals` non-empty | You repeated near-identical calls. Do not retry the same thing; diagnose instead. | | Cost spike in `usage` | Check `usage --by model`: are you using a bigger model than the task needs? | ## Digging deeper ```bash clawmetry sessions --active # who is running clawmetry sessions <SID> --transcript # what actually happened clawmetry sessions <SID> --cost # where the money went (incl. sub-agents) clawmetry sessions <SID> --errors # error events only clawmetry activity --follow --max-events 50 # live NDJSON event stream clawmetry usage --efficiency # A-F efficiency grade ``` Exit codes: `0` ok, `3` no data source (skip), `4` feature needs an upgrade (stderr carries a JSON body with `upgrade_url`; surface it to your human).

Frequently asked questions