ai-quota-check

What This Skill Does

The ai-quota-check skill is the definitive dashboard for OpenClaw users to monitor their AI provider limitations. Instead of manually checking each service, this tool aggregates data from Antigravity, Copilot, and Codex into a single, clean interface. It identifies your current login status, active usage, and provides intelligent model recommendations based on real-time quota availability. By tracking usage against a 20% fallback threshold, the skill automatically suggests the most efficient path for your tasks, ensuring you never hit a hard lockout mid-project.

Installation

To install this skill, use the ClawHub command-line interface. Open your terminal and execute the following command to pull the latest version from the repository:

clawhub install openclaw/skills/skills/kr1json/ai-quota-check

Once installed, the skill will be registered in your OpenClaw environment, allowing you to trigger it via natural language requests or automated cron jobs.

Use Cases

• Pre-session planning: Run a quota check before starting a large project to see which model tiers are available.
• Dynamic Fallback: Automatically pivot from a saturated provider to a secondary or tertiary model based on the suggested routing rules.
• Reset Monitoring: Use the skill to identify when daily or weekly limits have refreshed, allowing you to resume using premium models.
• Developer Workflow: Optimize coding and debugging tasks by using the recommended model hierarchy (GPT-5.3-Codex vs Gemini-3-Pro).

Example Prompts

• "쿼타 확인해줘"
• "What is my current quota status across all providers?"
• "Can you recommend the best model for a complex reasoning task based on my current usage?"

Tips & Limitations

• Always execute raw: When the tool returns data, do not attempt to paraphrase the output. The dashboard is designed for high-density information display and should be kept as-is.
• Threshold awareness: The 20% threshold is the hard-coded trigger for model switching. If your preferred model is below this, the tool will prioritize stability over model preference.
• Cron optimization: If you have the skill running on a cron schedule, ensure your environment variables for provider logins are correctly synced to avoid false-negative login warnings.