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.
94
93%
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 strong skill description that clearly defines what the skill does (summarize per-model usage/cost data from CodexBar CLI) and when to use it (when asked for model-level cost data or scriptable summaries). It uses natural trigger terms and is highly distinctive due to the specific tool name and narrow domain focus.
| 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, well-defined 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', 'cost JSON', 'Codex', 'Claude'. 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
87%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-crafted, concise skill that provides actionable CLI commands with clear examples for multiple use cases. The progressive disclosure is good with a clean reference to external docs. The main weakness is the lack of error handling or validation guidance—what to do when commands fail or JSON is unexpected.
Suggestions
Add a brief troubleshooting or validation note (e.g., what to check if codexbar CLI is not found, or if the JSON output has no modelBreakdowns).
| 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 CLI commands with concrete flags and options. The examples cover multiple modes (current, all, json output) and multiple input methods (CLI, file, stdin), all copy-paste ready. | 3 / 3 |
Workflow Clarity | The quick start provides a basic two-step sequence, and the 'Current model logic' section explains fallback behavior clearly. However, there's no validation or error handling guidance—what happens if codexbar isn't installed, if the JSON is malformed, or if no modelBreakdowns exist? For a data-processing workflow this is acceptable but not exemplary. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections (Quick start, Current model logic, Inputs, Output) and a single-level reference to `references/codexbar-cli.md` for deeper CLI details. Appropriate split between overview and reference material. | 3 / 3 |
Total | 11 / 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 | |
- Repository
- trpc-group/trpc-agent-go
- Commit
af8bd5f
- 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.