Minimax Usage

Monitor Minimax Coding Plan usage to stay within API limits. Fetches current usage stats and provides status alerts.

Before installing or running this skill: 1) Do not assume the metadata lists required credentials — the script expects MINIMAX_CODING_API_KEY and MINIMAX_GROUP_ID. 2) Inspect and fix the .env sourcing path: SKILL.md says create .env next to the script but the script sources ../../.env. Either place your .env two levels up (risky) or edit the script to source a local .env (e.g., source "$(dirname "$0")/.env"). 3) Ensure jq and curl are available (jq is used but not declared). 4) Keep the .env file minimal — only include the two Minimax values; don't put other secrets in that file if you keep it at ../../.env. 5) Run the script in an isolated environment (container or sandbox) until you confirm it behaves as expected. 6) Prefer the registry metadata to be updated to declare the env vars and required binaries; if you cannot verify or change the script, treat this skill as untrusted.

Type: OpenClaw Skill Name: minimax-usage Version: 1.0.1 The skill bundle is designed to monitor Minimax API usage. The `minimax-usage.sh` script uses `curl` to query the legitimate Minimax API endpoint, authenticating with an API key sourced from a `.env` file. While there is a discrepancy between the `SKILL.md` instructions for `.env` file placement and the script's actual path (`../../.env`), this appears to be a functional bug or a common pattern for shared environment variables, not an attempt at data exfiltration or malicious access. There is no evidence of prompt injection, unauthorized execution, persistence mechanisms, or obfuscation. All actions align with the stated purpose of monitoring API usage.