model-usage

Use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.

3.70x

Quality

84%

Does it follow best practices?

Impact

100%

3.70x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

79%

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

This is a well-structured, concise skill that provides actionable CLI commands and clear input/output descriptions. Its main weaknesses are the lack of error handling or validation guidance in the workflow, and the inability to verify that referenced bundle files (scripts/model_usage.py, references/codexbar-cli.md) actually exist. The content is appropriately scoped and avoids unnecessary verbosity.

Suggestions

Add a brief error handling note (e.g., what to do if codexbar is not installed, or if the JSON output is empty/malformed) to improve workflow clarity.

Ensure bundle files (scripts/model_usage.py, references/codexbar-cli.md) are included so the skill's references can be validated and progressive disclosure is fully supported.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. Every section serves a purpose, there's no explanation of basic concepts, and the TODO note is appropriately brief. The skill assumes Claude's competence throughout.	3 / 3
Actionability	Provides fully executable bash commands with clear flag combinations for different use cases. The input section shows concrete piping and file-based alternatives. The current model logic section gives specific fallback behavior.	3 / 3
Workflow Clarity	The quick start provides a clear two-step process, and the current model logic explains fallback behavior well. However, there are no validation or error-handling steps — what happens if codexbar isn't installed, if the JSON is malformed, or if the provider is invalid? For a CLI-based workflow, some error feedback guidance would strengthen this.	2 / 3
Progressive Disclosure	References a bundled script and a references file, but no bundle files were provided to verify these exist. The reference to `references/codexbar-cli.md` is one-level deep and well-signaled, but the skill could better organize the 'Current model logic' section — it reads more like internal documentation than a quick-reference guide.	2 / 3
	Total	10 / 12 Passed

Description

89%

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

This is a solid description that clearly identifies its niche (CodexBar CLI cost usage), provides explicit trigger conditions, and uses natural keywords a user would employ. The main weakness is that the specific capabilities could be more concretely enumerated beyond 'summarize per-model usage' to better differentiate the range of actions supported.

Suggestions

List more specific concrete actions (e.g., 'parse codexbar cost JSON', 'compare costs across models', 'display current session spend') to improve specificity.

Dimension	Reasoning	Score
Specificity	It names the domain (CodexBar CLI cost usage) and describes some actions (summarize per-model usage, current model or full model breakdown), but the specific concrete actions are somewhat limited—it doesn't enumerate distinct operations like 'parse JSON output', 'generate cost reports', 'compare model costs' etc.	2 / 3
Completeness	Clearly answers both 'what' (summarize per-model usage for Codex or Claude, including current model or full breakdown) and 'when' (explicit trigger clause: 'Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON').	3 / 3
Trigger Term Quality	Includes strong natural trigger terms: 'model-level usage', 'cost data', 'codexbar', 'per-model summary', 'codexbar cost JSON', 'Codex', 'Claude', 'model breakdown'. These cover the terms a user would naturally use when asking about cost/usage data from CodexBar.	3 / 3
Distinctiveness Conflict Risk	Very specific niche—CodexBar CLI cost/usage data with per-model breakdowns. The combination of 'codexbar', 'cost', 'per-model', and 'CLI' makes it highly unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	9 / 11 Passed

Repository: attilaczudor/Test
Commit: b4fc4af

Reviewed: 2 months 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.