SKILLEMALL.ai

BF codex-account-switcher

Manage multiple OpenAI Codex accounts by capturing current login tokens, switching between saved accounts, and auto-selecting the best one based on quota budget scoring. Can also explicitly sync saved Codex tokens into OpenClaw agent auth stores on this machine. Sensitive: reads and writes local authentication files.

ClawHub Agent Skills author: Oliver Drobnik v1.4.3 MIT-0 4 files body ≈ 1 448 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 42/100 · Will not run — References files that are not bundled: ../quota-dashboard/

GeneratorSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
99
Quality 40%
67
Run on models
none yet
Process rating
F
42/100
Will not run
References files that are not bundled: ../quota-dashboard/
Tools and files w 18
0
Result and completion w 14
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-high-entropy-token SKILL.md:172
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    {"timestamp": 1774878000, "account": "oliver", "user_id": "user…bew"}
    quoted

Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: ../quota-dashboard/
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "summary"

Process rating: all ten parameters 42/100

Will not run. References files that are not bundled: ../quota-dashboard/
  • 0Tools and files. 1 referenced file(s) missing: ../quota-dashboard/
  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 21 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1448 tokens
  • 100Progress reporting. Reports progress

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 318: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 21 items
  • +4Has examples (9 code blocks)
  • +3All 1 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.

External checks

ClawHub: suspicious
The skill mostly matches its stated account-switching purpose, but it needs review because it rewrites and duplicates login tokens, performs some of that persistence silently, and does not safely contain account-name file paths.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026