setup-minimax
Skill1 starsChanged 9 months agoMITView on GitHub
Configure NanoClaw + Claude Code to use MiniMax via the Anthropic-compatible endpoint. Use when user says "minimax", "MiniMax-M2.5", "anthropic compatible", "base url", or wants cheaper tokens with Claude Code.
- Reads credentials
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-gmailSkill
- add-mcp-skeletonSkill
- add-parallelSkill
- add-telegramSkill
- add-telegram-swarmSkill
- add-voice-transcriptionSkill
- convert-to-dockerSkill
- customizeSkill
- debugSkill
- pr-reviewSkill
- setup-macmini-24x7Skill
- setupSkill
- x-integrationSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 24
Do NOT commit secrets to git.
- Very specific: line 55
If you want to use a .env, keep it minimal and gitignored:
- Distinctive: line 72
Run NanoClaw and trigger an agent run.
- Distinctive: line 74
If Apple Container is used:
- Distinctive: line 79
If Docker is used:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Setup MiniMax (Anthropic-Compatible)
Goal: make NanoClaw containers call MiniMax (not Anthropic) using the Anthropic-compatible API.
1) Preconditions (macOS)
Check runtime:
uname -s
which container && container system status || true
which docker && docker info >/dev/null 2>&1 && echo "docker ok" || trueNanoClaw can run on Apple Container or Docker. Prefer Apple Container on Apple silicon if already installed.
2) Configure Host Environment Variables
Do NOT commit secrets to git.
Required:
MINIMAX_API_KEY(your MiniMax key)
Recommended:
ANTHROPIC_BASE_URL=https://api.minimax.io/anthropicANTHROPIC_MODEL=MiniMax-M2.5ANTHROPIC_SMALL_FAST_MODEL=MiniMax-M2.5ANTHROPIC_SMALL_MODEL=MiniMax-M2.5ANTHROPIC_SMALL_REASONING_MODEL=MiniMax-M2.5ANTHROPIC_SONNET_MODEL=MiniMax-M2.5
Optional:
API_TIMEOUT_MS=3000000CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1
Sanity check (should print without errors, but never print the key):
echo "${MINIMAX_API_KEY:+MINIMAX_API_KEY set}"
echo "${ANTHROPIC_BASE_URL:-missing}"
echo "${ANTHROPIC_MODEL:-missing}"3) Configure NanoClaw Auth
NanoClaw passes secrets to the agent container via stdin. It can read:
.envin the project root (keys:CLAUDE_CODE_OAUTH_TOKENorANTHROPIC_API_KEY)- host env vars as a fallback (recommended for MiniMax)
If you want to use a .env, keep it minimal and gitignored:
cat > .env <<'EOF'
# Secrets (optional). Prefer host env vars.
# ANTHROPIC_API_KEY=...
EOF4) Build Agent Image
./container/build.sh5) Verify in Practice
Run NanoClaw and trigger an agent run. If the key is wrong you will see an auth error.
If Apple Container is used:
container system statusIf Docker is used:
docker info >/dev/nullDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

