cli-cost-usage

View cost breakdowns, token usage, and call logs from the CLI. Filter by provider, model, or date range. Export usage reports and inspect per-connection spending.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/cli-cost-usage/SKILL.md

Quality

Content

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

The body is a reasonably concise CLI reference catalog, but it is flat rather than a workflow, shows bare commands without demonstrating flag usage, and inlines everything in one file with no progressive disclosure. Adding worked examples, validation guidance for the mutating subcommands, and splitting per-subcommand detail into reference files would materially improve it.

Suggestions

Replace bare `omniroute cost`-style examples with at least one invocation that exercises the listed flags (e.g. `omniroute cost --since 2026-07-01 --group-by model --limit 20`).

Add validation/confirmation guidance for stateful commands (`usage set`, `usage reset`) — e.g. check `usage get` or `usage budget` before and after to confirm the change took effect.

Move the bulk per-subcommand flag reference into a separate reference file and keep SKILL.md as an overview pointing to it, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of concept explanations Claude already knows — just flags and bare command examples — but the repetitive Flags:/Example: scaffolding per subcommand and many no-arg examples add minor padding, keeping it just below the fully-lean score-5 anchor.	4 / 5
Actionability	Commands and flags are named but most examples are bare invocations (e.g. `omniroute cost` with none of its --period/--group-by flags shown), so the guidance is concrete but incomplete rather than copy-paste ready, matching the score-3 anchor.	3 / 5
Workflow Clarity	This is a flat command catalog with no multi-step workflow or validation; per the rubric's destructive/batch cap, stateful commands like 'usage set <amount>' and 'usage reset [scope]' lack any validate/verify checkpoint, capping workflow_clarity at 3 even though individual commands are unambiguous.	3 / 5
Progressive Disclosure	A single SKILL.md inlines all ~25 subcommands with section headers but no bundle files and no splitting of the reference bulk into separate files, so structure exists but content that would benefit from being separated stays inline, matching the score-3 anchor.	3 / 5
	Total	13 / 20 Passed

Description

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

The description is specific and action-rich with a clear niche, but it omits any 'Use when...' trigger guidance, capping its completeness. Adding explicit trigger phrases and a few user-synonyms (spend, billing) would raise both completeness and trigger quality.

Suggestions

Append a 'Use when...' clause naming concrete trigger phrases (e.g. 'Use when reviewing spend, token usage, or per-connection cost from the CLI').

Add common user synonyms like 'spend', 'billing', or 'invoices' to broaden trigger-term coverage.

Confirm whether 'cost' vs 'usage' vs 'pricing' subcommands map to distinct user intents to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'View cost breakdowns, token usage, and call logs', 'Filter by provider, model, or date range', 'Export usage reports and inspect per-connection spending' — with comprehensive coverage, matching the score-5 anchor.	5 / 5
Completeness	Has a clear 'what' (the actions above) but no 'when'/'Use when' trigger guidance, so per the rubric's explicit cap a missing trigger clause limits completeness to 3.	3 / 5
Trigger Term Quality	Good natural-term coverage ('cost breakdowns', 'token usage', 'call logs', 'usage reports') but missing common synonyms a user might say like 'spend', 'billing', or 'invoice', so it sits just below the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	Targets a distinct niche (CLI cost/usage analytics for omniroute) with low overlap risk, though a few trigger phrases are generic enough to leave minor overlap risk rather than reaching the clearly-niched score-5 anchor.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: diegosouzapw/OmniRoute
Path: skills/cli-cost-usage/SKILL.md
Commit: ea0cdc5

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.