CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

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

86%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 well-engineered orchestration body: exact commands, explicit routing tables, a prescribed output contract, and clean progressive disclosure into real reference files. The main improvable spots are the duplicated haiku cost note and the absence of error-recovery guidance for helper or scope-parse failures.

DimensionReasoningScore

Conciseness

The body is efficient, operational, and assumes Claude's competence (no concept explanations), but the '/model haiku' cost advice is repeated nearly verbatim in both the intro and 'Why this is a separate skill', and that rationale section is mildly discretionary. Efficient with minor trims available — the 4 anchor.

4 / 5

Actionability

Fully executable guidance: the exact helper command 'python3 scripts/audit-extract.py $ARGUMENTS[1] --mode $ARGUMENTS[0]', exact output-path templates (audit_<id8>_<ts>_<mode>.json/.md), verbatim usage text to print, and exact status lines. Copy-paste ready with specific handling for the common cases.

5 / 5

Workflow Clarity

A clearly sequenced 5-step workflow with an explicit input-validation checkpoint (missing/invalid path → print usage and stop), dispatch and scope-routing tables, and a prescribed write order. It falls short of 5 because there is no error-recovery path for helper failure or an unexpected digest.scope value; it is above 3 because checkpoints are explicit, and the read-only analysis does not trigger the destructive/batch cap.

4 / 5

Progressive Disclosure

A clear overview that routes to one-level-deep references: all five referenced files exist in references/, two routing tables (argument dispatch and scope×mode) plus an annotated per-scope reference listing make navigation unambiguous, with detail correctly split out of SKILL.md.

5 / 5

Total

18

/

20

Passed

Description

92%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.

A strong description: concrete capabilities, explicit multi-trigger 'when' guidance, and a distinct niche. The only weakness is trigger-term breadth — a few natural user phrasings (cost/spend/token usage) and file-extension mentions are absent.

DimensionReasoningScore

Specificity

Multiple concrete actions are stated — 'Audit a session-metrics JSON export for token-usage waste and produce a plain-English findings report' — with both modes enumerated ('ratios + cache health + top expensive turns/sessions', 'adds CLAUDE.md / settings / re-read scan') and three scopes. Coverage is comprehensive with no gaps, matching the 5 anchor rather than the 4 anchor's 'minor gaps'.

5 / 5

Completeness

Explicitly answers both what (audit a session-metrics JSON export for token-usage waste, produce a plain-English findings report) and when ('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') with concrete trigger phrases — a clear 5.

5 / 5

Trigger Term Quality

Good natural-term coverage: 'audit / review / find waste in a saved session-metrics JSON', the slash command '/audit-session-metrics', and 'after an HTML export'. A few natural terms users might say are missing (e.g. 'token usage', 'cost', 'spend', file-extension variants), so it sits at the 4 anchor rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche tied to a named artifact (session-metrics JSON exports) and a named slash command, with mode and scope vocabulary that no generic skill would share. Minimal conflict risk, matching the 5 anchor.

5 / 5

Total

19

/

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
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.