claude-quota-checker_skill

Overview

This skill checks how much Claude Max / Claude Pro subscription quota you have left, not how much you spent. It reports remaining percentages for the current session and weekly windows, shows plan type, and gives exact reset times. It automates the Claude Code CLI via a temporary tmux session—no API keys or admin access required.

How this skill works

The script creates a temporary tmux session with a scratch git repo, launches the Claude Code CLI, and sends the /usage command. It captures and parses the CLI output to extract plan type, session and weekly usage percentages, and reset times. Finally it cleans up the tmux session and returns a concise status report.

When to use it

• You want to know if you are about to hit your Claude subscription limit
• Diagnosing slow or rate-limited Claude behavior
• Before starting a large session or batch of prompts
• When asked: “How much Claude do I have left?” or “Am I rate limited?”
• When you need the exact weekly reset time

Best practices

• Run from the skill directory or invoke with the full path so the script auto-detects its location
• Ensure claude CLI is installed and authenticated before running to avoid hangs
• Install tmux and git on your machine (macOS or Linux) to meet requirements
• If the script hangs >15s, kill the tmux session (tmux kill-session -t cu-*) and re-authenticate if needed
• Treat this as a subscription-status diagnostic, not an API billing checker

Example use cases

• Quickly check remaining session quota before a long conversation or code run
• Triage slow responses: verify you haven’t hit weekly or session limits
• Automated pre-job check in a local workflow to avoid mid-job interruptions
• Support agents confirming a user’s remaining quota and reset time
• Simple health check for teams using personal Pro/Max accounts