Minimax Usage

**Judgement:** A focused, practical skill that reliably reports Minimax Coding Plan usage and basic status; valuable for teams actively using Minimax’s Coding Plan and needing quota awareness, but narrow in scope and dependent on Minimax’s specific endpoint and headers. **What it does well:** - Automates retrieval of current Coding Plan usage (used vs. remaining prompts, reset window) via the official Minimax API. - Provides a simple status interpretation (e.g., GREEN at low usage, configurable threshold mindset like 60%). - Straightforward configuration using environment variables (`MINIMAX_CODING_API_KEY`, `MINIMAX_GROUP_ID`). **Key risks / limitations:** - Depends entirely on a single Minimax endpoint and specific header patterns (including referer and user-agent); any API or auth change could break the skill. - Requires secure handling of the dedicated Coding Plan API key in environment variables; misconfiguration or leakage would expose quota and potentially billing-related data. - Functionality is intentionally narrow: monitoring and alerts only; it does not manage, predict, or optimize usage beyond simple thresholding. - Likely assumes a Unix-like shell environment and network access, which could limit portability in some deployments. **Recommended scenarios:** - Teams using Minimax Coding Plan in production or shared environments who need a lightweight guardrail to avoid hard quota hits. - CI/CD or scheduled jobs that should only proceed when sufficient Coding Plan capacity is available. - Operational monitoring scripts or dashboards where Coding Plan health (usage, buffer, reset time) is one of several service checks. - Individual developers who frequently rely on Minimax Coding Plan and want a quick, scriptable usage snapshot before running expensive workflows.