Openclaw Skill Minimax Tracker

v0.1.0

Track and monitor MiniMax API usage with real-time progress bars, automatic resets, and scheduled reminders for OpenClaw agents.

0· 281·0 current·0 all-time
by魏然@qiaotucodes
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (MiniMax usage tracker) matches the included Python script and SKILL.md. Required capabilities (none) are proportional to the stated purpose — the skill only reads/writes a local JSON file and prints progress bars.
Instruction Scope
SKILL.md instructs the agent to invoke the provided script (via subprocess) and to optionally install/copy the skill into the workspace; it does not direct reading of unrelated system files, collection of secrets, or network exfiltration. Integration examples run the local script, which is expected behavior for this skill.
Install Mechanism
No install spec is present (instruction-only with an included script). Nothing is downloaded or executed from external URLs; the README suggests cloning a GitHub repo but the packaged files include the script. This is low-risk from an install perspective.
Credentials
The skill declares no environment variables, no credentials, and no config paths beyond writing to a user-scoped JSON file (~/.openclaw/workspace/minimax_usage_data.json). That storage need is proportional to a usage-tracking utility.
Persistence & Privilege
The skill is not force-included (always:false) and does not request persistent elevated privileges or modify other skills. It only writes its own JSON file in the user's home workspace.
Assessment
This skill appears coherent and low-risk: it only records prompt counts in a JSON file and prints progress bars. Before installing, review/verify the GitHub source (SKILL.md points to a repo) if you don't already trust it. Note that the script writes to ~/.openclaw/workspace/minimax_usage_data.json (check file ownership/permissions). The reset-time logic uses the system local time (the code assumes an UTC+8 reset window but uses naive datetime.now(), which may produce incorrect reset calculations on systems in other timezones) — if correct reset timing is important, review or test that behavior. If you want stronger isolation, run the script in a restricted environment (container or limited-permission user). There are no network calls or credential requests in the packaged code.

Like a lobster shell, security has layers — review code before you run it.

latestvk978epapsgxyp91gep6kavcyh581z7k2

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments