AB claude-quota-checker
Check how much Claude Max / Claude Pro subscription quota you have LEFT — not how much you spent. Most usage tools track API billing or token costs. This one answers the real question: 'Am I about to hit my limit?' Shows remaining % for session and weekly windows, plan type, and exact reset times. Works by automating Claude Code CLI's /usage command via tmux — no API keys, no Admin keys, no reverse engineering. Just your subscription status, instantly. Use whenever someone asks: 'how much Claude do I have left', 'am I rate limited', 'when does my quota reset', 'check my usage', 'claude limits', '还剩多少', '查用量', '还能用吗', 'why is Claude slow'. Also use as a first diagnostic when the user hits rate limits or Claude feels sluggish.
As a process B 78/100 · Nearly there — weak spots: running it twice
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 3. 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 78/100
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 18 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 526 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)
- +1No license
- +2Single-language instructions
- +3Description length 734: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 18 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.