minimax-usage

What This Skill Does

The minimax-usage skill acts as a dedicated monitoring agent for your Minimax Coding Plan. Managing API limits can be difficult when working with high-frequency coding tasks or large-scale automation, and this skill eliminates the manual burden of checking the platform dashboard. It connects directly to the Minimax API to fetch real-time quota data, processing the number of prompts used versus your total allowance. The skill provides clear, color-coded status updates (Green, Yellow, Red) based on your consumption rate, ensuring you never hit a hard block during critical development work.

Installation

To integrate this skill into your environment, use the OpenClaw CLI: clawhub install openclaw/skills/skills/franky0617/minimax-coding-plan-usage. After installation, create a .env file in the script directory containing your MINIMAX_CODING_API_KEY and MINIMAX_GROUP_ID. You can retrieve your Group ID from the basic information section of the Minimax developer portal. Ensure your environment has basic shell execution permissions to run the monitoring script successfully.

Use Cases

This skill is perfect for developers managing team-shared API accounts, individual power users optimizing their budget, and automated CI/CD pipelines that need to verify availability before triggering high-volume jobs. It is particularly useful for preventing 'API exhaustion' mid-project, allowing users to pause intensive tasks when they hit a threshold.

Example Prompts

1. "OpenClaw, can you check my current Minimax coding plan usage?"
2. "How much of my prompt quota do I have left for today?"
3. "Should I pause my current code generation tasks based on my Minimax usage stats?"

Tips & Limitations

Keep in mind that the usage tracking follows a dynamic 5-hour reset window. This means your 'Used' count is not a daily total but a rolling window of active consumption. Because the Coding Plan API key is exclusive, ensure you do not confuse it with standard Minimax LLM keys. The current target threshold is set to 60%; if your usage exceeds this, prioritize batching your coding tasks to stay within the safe buffer. Always double-check your .env configuration if you receive authentication errors, as the headers require specific user-agent strings provided in the base implementation.