CtrlK
BlogDocsLog inGet started
Tessl Logo

codexbar

AI service usage/quota via CodexBar CLI: Codex/OpenAI, Claude, Kimi and other provider limits, credits, reset times.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 an exemplary lean skill: executable commands, non-obvious operational gotchas, and clean sectioning with no filler. Its only minor gap is the absence of an explicit ordered workflow, which is acceptable for a simple single-purpose query skill.

DimensionReasoningScore

Conciseness

The body is lean and information-dense: it never explains concepts Claude already knows and every line is either an executable command or a non-obvious gotcha that earns its place.

5 / 5

Actionability

Provides copy-paste-ready commands (`codexbar usage --provider codex --json`, flag sets like `--account`, `--all-accounts`) and concrete verification (`claude-swap list --token-status`) covering the common cases.

5 / 5

Workflow Clarity

For a simple query skill the guidance is clear with useful conditional branches (CLI unavailable → open dashboard; zero bytes → Gatekeeper prompt) and a verification signal, but there is no explicit sequenced workflow with checkpoints.

4 / 5

Progressive Disclosure

Self-contained with no external references needed and well-organized into clear sections (CLI, Auth model, Dashboard endpoints, Interpreting output); no nested or buried references.

5 / 5

Total

19

/

20

Passed

Description

70%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 clearly niched around CodexBar for AI-provider usage/quota, but it omits an explicit "Use when..." trigger clause, which caps its completeness. Adding trigger phrasing would lift the score meaningfully.

Suggestions

Append an explicit "Use when..." trigger clause (e.g., "Use when the user asks about AI subscription usage, remaining credits, rate limits, or reset times") to raise completeness.

Add common synonyms like "rate limits" and "billing" alongside "limits" and "credits" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete capabilities — "provider limits, credits, reset times" — rather than vague abstractions, though a few aspects of quota reporting are not enumerated.

4 / 5

Completeness

Has a clear "what" (AI service usage/quota via CodexBar CLI) but no explicit "Use when..." trigger clause in the frontmatter, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural terms like "usage", "quota", "credits", "reset times", and provider names users would mention, though common variants like "rate limits" or "billing" are absent.

4 / 5

Distinctiveness Conflict Risk

Names a specific tool (CodexBar CLI) and a narrow niche (AI provider usage/quota), giving it distinct triggers with minimal overlap risk.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
steipete/agent-scripts
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.