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

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

57%

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 well-organized command catalog but is thin on actionable detail: flags lack descriptions, examples are bare, and mutating commands have no validation steps. It reads as auto-generated reference stubs rather than instructive guidance.

Suggestions

Add a one-line description for each flag and at least one realistic example showing flags in use (e.g. 'omniroute usage logs --since 7d --follow').

Remove the duplicated Overview paragraph or replace it with a brief orientation that does not repeat the frontmatter description.

For mutating commands (usage set/reset, pricing set), note expected output or a verification step so users can confirm the change took effect.

Dimension	Reasoning	Score
Conciseness	It avoids concept explanation, but the Overview duplicates the frontmatter description verbatim and the per-subcommand examples are bare repetitions ('omniroute cost', 'omniroute pricing') that add little per token.	2 / 3
Actionability	Commands are concrete, but flags are listed without descriptions or example values and the examples only show the bare invocation with no flags demonstrated, leaving key details missing.	2 / 3
Workflow Clarity	This is a flat command reference with no multi-step sequence, and mutating commands like 'usage set' and 'usage reset' lack any validation/verification guidance, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	With no bundle files needed, the body is well-organized into clearly headed subcommand groups (cost, pricing, usage) that make navigation easy, satisfying the simple-skill guidance.	3 / 3
	Total	9 / 12 Passed

Description

82%

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 trigger-rich with a clear niche, but it lacks an explicit 'when to use' clause, which caps its completeness. Adding a 'Use when…' sentence would round it out.

Suggestions

Append an explicit trigger clause such as 'Use when the user asks about CLI spending, token usage, or cost reports.' to raise completeness.

Consider adding common phrasings like 'how much did I spend' or 'API costs' to broaden natural trigger coverage.

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' — rather than vague language.	3 / 3
Completeness	It clearly answers 'what does this do' but provides no 'Use when…' or equivalent explicit trigger guidance, so per the rubric completeness is capped at 2.	2 / 3
Trigger Term Quality	Includes natural terms a user would say — 'cost breakdowns', 'token usage', 'call logs', 'usage reports', 'provider', 'model', 'date range' — with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The cost/usage-tracking niche is distinct with clear triggers around spending and token usage, making it unlikely to fire for the wrong skill.	3 / 3
	Total	11 / 12 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: 3070925

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.