1.6 KiB
1.6 KiB
Context Offloading with /ask-minimax
/ask-minimax delegates a task to a MiniMax M3 sub-session that reads and writes files directly. Only a short summary flows back — file contents never load into this session. Reach for it when the file payload dwarfs the answer payload.
Use it for
- Summarising large files (logs, dumps, generated reports >500 lines)
- Extracting specific facts from multiple files or long reference docs
- Generating big files (migrations, config bundles, fixtures, large docs) where the content does not need to flow back
- Format conversion of large files (CSV↔JSON, XML↔YAML, etc.)
- Bulk find-and-extract across many files where only the matches matter
Skip it for
- Iterative design or debugging — the main session needs the content in context
- Small files (under a few hundred lines) — overhead exceeds savings
- Tasks where you will immediately re-read the result to act on it
- Anything requiring tools MiniMax cannot use (web fetch, MCP, browser, agent dispatch)
- Architecture or quality-sensitive output — MiniMax is for grunt work, not nuanced reasoning
How to delegate
Pass file paths, not file contents. If you read the input files yourself before invoking, you have already paid the token cost the skill exists to avoid.
Failure handling
MiniMax intermittently returns invalid system role and other transient errors. Retry once. If it fails again, fall back to a Claude subagent with the same brief — Sonnet for file-heavy grunt work, Opus for reasoning-grade consults. Never silently drop the task. Log new error shapes to the project's memory/gotchas-*.md.