← Back to Skills Marketplace
3772
Downloads
1
Stars
16
Active Installs
2
Versions
Install in OpenClaw
/install minimax-usage
Description
Monitor Minimax Coding Plan usage to stay within API limits. Fetches current usage stats and provides status alerts.
Usage Guidance
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.
Capability Analysis
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.
Capability Tags
Capability Assessment
Purpose & Capability
The skill's stated purpose (monitor Minimax coding-plan usage) matches what the script does (HTTP GET to minimax platform using an API key and GroupId). However the registry metadata declares no required environment variables or credentials while both SKILL.md and the script require MINIMAX_CODING_API_KEY and MINIMAX_GROUP_ID. This mismatch is incoherent and should have been declared.
Instruction Scope
SKILL.md instructs the user to create a .env 'in the same directory as the script', but the script actually sources "$(dirname "$0")/../../.env" (two directories up). That difference means the script may read a .env in an unexpected location (potentially unrelated environment data). The script only sends data to platform.minimax.io (expected), and does not appear to exfiltrate to other endpoints, but the incorrect source path is a scope creep/risk because it can pull in variables the author didn't intend.
Install Mechanism
No install spec (instruction-only plus a shell script). Nothing is downloaded or written during an install step, which is low risk. The provided script is executed locally and not installed from remote URLs.
Credentials
The script needs MINIMAX_CODING_API_KEY and MINIMAX_GROUP_ID (proportionate to the task). However the registry lists no required env vars (incoherent). Additionally the script sources a .env file from ../../.env which could load many other environment variables not intended for this skill; that's a proportionality risk. The script also relies on jq and curl but required binaries were not declared in metadata.
Persistence & Privilege
The skill does not request permanent presence (always:false). It does not modify other skills or system-wide settings and does not persist credentials; it simply reads variables and makes a single API call. Autonomous invocation is enabled by default (normal).
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install minimax-usage - After installation, invoke the skill by name or use
/minimax-usage - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
Fixed GroupId URL to point to basic-information page
v1.0.0
Initial release of minimax-usage skill.
- Monitors usage of Minimax Coding Plan to help users stay within API limits.
- Fetches current usage stats and provides easy-to-understand status alerts.
- Guides users through setup with required environment variables.
- Documents API endpoint, required headers, and output examples.
- Describes plan-specific metrics and usage reset logic.
Metadata
Frequently Asked Questions
What is Minimax Usage?
Monitor Minimax Coding Plan usage to stay within API limits. Fetches current usage stats and provides status alerts. It is an AI Agent Skill for Claude Code / OpenClaw, with 3772 downloads so far.
How do I install Minimax Usage?
Run "/install minimax-usage" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Minimax Usage free?
Yes, Minimax Usage is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Minimax Usage support?
Minimax Usage is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Minimax Usage?
It is built and maintained by Seth Rose (@thesethrose); the current version is v1.0.1.
More Skills