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.
92
89%
Does it follow best practices?
Impact
100%
3.70xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 well-crafted skill description that clearly specifies what the skill does (summarize per-model usage/cost data from CodexBar CLI), includes explicit trigger conditions, and uses natural keywords a user would employ. The description is concise, uses third-person voice, and occupies a clear niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'summarize per-model usage', 'current (most recent) model', 'full model breakdown', and 'scriptable per-model summary from codexbar cost JSON'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('summarize per-model usage for Codex or Claude, including current model or full model breakdown') and when ('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', 'Codex', 'Claude', 'cost JSON'. These cover the terms a user would naturally use when asking about usage costs from CodexBar. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific tool name 'CodexBar CLI' and the narrow domain of per-model cost/usage summaries. Unlikely to conflict with other skills given the specific tool and data format references. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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 for per-model usage summarization. Its main weaknesses are the lack of validation/error-handling steps in the workflow and the inability to verify referenced bundle files. The content is appropriately scoped and avoids unnecessary explanation.
Suggestions
Add a brief troubleshooting or validation step (e.g., 'Verify codexbar is installed: `codexbar --version`; if the command fails, see references/codexbar-cli.md for installation').
Ensure the bundle includes the referenced files (`scripts/model_usage.py` and `references/codexbar-cli.md`) so the skill is self-contained and references can be validated.
| 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. No unnecessary padding or explanation of things Claude already knows. | 3 / 3 |
Actionability | Provides fully executable CLI commands with concrete flags and options. The quick start, input examples, and output format options are all copy-paste ready with specific provider/mode combinations demonstrated. | 3 / 3 |
Workflow Clarity | The steps are listed (fetch JSON, run script) but there's no validation or error handling guidance. What happens if codexbar CLI isn't installed? What if the JSON is malformed? The 'current model logic' section explains fallback behavior well, but there are no explicit checkpoints or feedback loops. | 2 / 3 |
Progressive Disclosure | References a bundled script at `{baseDir}/scripts/model_usage.py` and `references/codexbar-cli.md`, but no bundle files were provided to verify these exist. The structure is reasonable with clear sections, but the reference to codexbar-cli.md cannot be validated, and the script itself is not available to confirm the documented flags work. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%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 | |
a5bf5e0
Table of Contents
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.