CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

audit-session-metrics

Audit a session-metrics JSON export for token-usage waste and produce a plain-English findings report. Trigger when the user runs /audit-session-metrics, when session-metrics suggests an audit after an HTML export, or when the user asks to audit / review / find waste in a saved session-metrics JSON. Two modes: "quick" (ratios + cache health + top expensive turns/sessions) and "detailed" (adds CLAUDE.md / settings / re-read scan). Supports session, project, and instance JSON scopes. Args: $ARGUMENTS[0] = quick|detailed, $ARGUMENTS[1] = path to a session-metrics JSON export.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strongly engineered workflow body — fully executable commands, precise dispatch and routing, and clean one-level progressive disclosure over a real reference bundle. Its main weakness is token efficiency: duplicated cost/model guidance across two sections, retained design-history rationale, and time-sensitive version details that belong in a single, trimmer block.

Suggestions

State the model-cost guidance once (either the intro or the 'Why this is a separate skill' section) and cut the duplicated provider/window details, dropping the historical model-pin explanation entirely.

Remove or heavily shrink the 'Why this is a separate skill' section — it justifies design decisions to maintainers, not instructions the executing model needs; if kept, isolate the version-sensitive model numbers (Haiku 5.5/4.5, window sizes) in a clearly marked section so they age visibly.

Add a validation branch to step 1 mirroring the input-path check: what to do when audit-extract.py exits nonzero or digest.scope is not one of session/project/instance (e.g., report the error and stop), closing the workflow's remaining checkpoint gap.

DimensionReasoningScore

Conciseness

The dispatch, steps, and output-contract sections are tight, but the body repeats the model/provider cost guidance almost verbatim in the intro and again in "Why this is a separate skill", retains historical rationale ("a hard model pin capped the usable context… broke invocation on long sessions") and a whole justification section the executing model does not need. It also carries time-sensitive version numbers (Haiku 5.5 / 4.5, 1M / 200k windows) outside any deprecated/old-patterns section — matching the "mostly efficient but includes some unnecessary explanation" anchor, not the level-4 anchor whose over-explanation is only minor.

3 / 5

Actionability

Everything is copy-paste executable: the exact helper invocation `python3 scripts/audit-extract.py $ARGUMENTS[1] --mode $ARGUMENTS[0]`, literal-equality dispatch on $ARGUMENTS[0], exact accepted file patterns, a verbatim usage message to print, exact output paths with derived <id8>/<ts> tokens, and an explicit write order ending with the two `[audit] saved →` lines. This matches the fully-executable anchor; the only deferred detail (findings content) is correctly delegated to the playbooks.

5 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced with an input validation checkpoint (missing/nonexistent path → print usage and stop) and an explicit write order, but there is no branch for the extract helper failing or `digest.scope` being unexpected, and no verify step for the written artefacts. This sits at "clear sequence with most checkpoints present; minor validation gaps" — above level 3 (which lacks checkpoints) but short of level 5's explicit error-recovery loops; the destructive/batch cap does not apply since the skill only reads input and writes new files.

4 / 5

Progressive Disclosure

The body is a genuine overview: a dispatch table and scope-routing table point to five real one-level-deep playbooks (all present in references/), organized per scope/mode with a closing reference listing, plus the extract script. Sibling cross-links between playbooks (e.g. detailed-audit.md ↔ quick-audit.md) stay one level from SKILL.md, matching the well-signaled clear-overview anchor.

5 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete capabilities, explicit multi-condition triggers with natural synonyms, mode/scope enumeration, and a distinct niche, all in third person and without padding. The Args documentation is invocation plumbing but stays brief and informative.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Audit a session-metrics JSON export for token-usage waste and produce a plain-English findings report" — and enumerates what each mode covers ("ratios + cache health + top expensive turns/sessions", "adds CLAUDE.md / settings / re-read scan") plus three JSON scopes. This matches the anchor for comprehensive, specific concrete actions rather than the level-4 anchor, which expects minor coverage gaps.

5 / 5

Completeness

Explicitly answers both questions: what it does (audit for token-usage waste, produce a plain-English findings report, with mode and scope detail) and when to trigger it (three concrete "Trigger when…" conditions including the slash command and the session-metrics suggestion path). This is the anchor-5 pattern of concrete trigger phrases paired with a clear capability statement.

5 / 5

Trigger Term Quality

Covers natural trigger phrases with synonyms — "runs /audit-session-metrics", "asks to audit / review / find waste in a saved session-metrics JSON" — alongside "token-usage", "cache health", and "session-metrics JSON". These are the exact words a user would say, matching the comprehensive synonym-plus-extension anchor; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche — auditing session-metrics JSON exports — with triggers tied to the specific /audit-session-metrics command and session-metrics exports, so it is unlikely to fire for unrelated skills. This matches the clear-niche/minimal-conflict anchor rather than the level-4 anchor's "minor overlap risk".

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

centminmod/my-claude-code-setup

Path

.claude/skills/audit-session-metrics/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.