SKILLEMALL.ai
GitHub ↗ RU Sign in

AB claude-code-usage

Check Claude Code OAuth usage limits (session & weekly quotas). Use when user asks about Claude Code usage, remaining limits, rate limits, or how much Claude usage they have left. Includes automated session refresh reminders and reset detection monitoring.

modbender/skill-library-mcp Agent Skills author: modbender MIT 8 files · 5 scripts body ≈ 1 483 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Check Claude Code OAuth usage limits (session & weekly quotas).

As a process B 65/100 · Nearly there — weak spots: when it triggers, running it twice, progress reporting

IntegrationAI and agentsSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
99
Quality 40%
78
Run on models
none yet
Process rating
B
65/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    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 Dangerous commands cmd-cron-mention CRON_SETUP.md:37
      Mentions editing / listing crontab
      crontab -e

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 65/100

    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 4 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 40 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1483 tokens
    • low 11 top-level sections: this looks like several domains in one skill

    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)
    • -4Absolute local paths (C:\Users, /home/…): not portable
    • -215 emoji in the instructions: noise for the model
    • -31 of 5 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 256: enough signal without eating the budget
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 40 items
    • +3Output format is stated explicitly
    • +4Has examples (15 code blocks)

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