Claude Code Usage

**Quick judgement** A focused, well-documented CLI skill that reliably surfaces Claude Code OAuth usage (session and weekly) and adds solid automation around reminders and reset detection. It’s strong for individual developers and lightweight monitoring setups on macOS/Linux, provided Claude Code CLI and system keychain tooling are correctly configured. **Key strengths** - Clear visibility into 5h and 7d usage with both human-friendly and JSON outputs. - Smart caching to avoid API spam while keeping results fresh. - Helpful automation scripts for precise session-refresh reminders and periodic reset detection. - Uses system credential stores rather than asking users to paste tokens. **Risks & limitations** - **Platform scope:** Only documented for macOS and Linux; no Windows support, and behavior may vary on non-standard environments or containers without Keychain/secret-tool. - **External dependencies:** Requires a working Claude Code CLI OAuth setup; any changes to Anthropic’s usage API or token storage could break the skill. - **Cron-based automation fragility:** Self-scheduling cron chains and polling scripts can be brittle if users edit/crontab manually, change paths, or rotate environments. **Recommended scenarios** - Individual developers heavily using Claude Code who want to avoid hitting limits unexpectedly. - Terminal-centric workflows that benefit from quick usage checks or statusline integration. - Simple monitoring/alerting for personal or small-team usage (e.g., Telegram notifications) without deploying full observability stacks. - Users comfortable with shell scripts and cron who want precise, low-overhead quota reset reminders.