Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingtai-ai/preset-skill-mimo
Official-source-led manual for the TUI `mimo` template.
Passed 18 of 22 test cases with the skill, and 6 of 22 without it.
and 17 more in the full report
12 fixed6 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
In `tui/internal/preset/preset.go`, what is the function or variable name where the built-in MiMo preset is defined?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies mimoPreset as the definition in tui/internal/preset/preset.go. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this child for the named built-in mimo preset. mimoPreset in tui/internal/preset/preset.go:1294 ships mimo-v2.5, XIAOMI_API_KEY, the OpenAI-compatible Xiaomi endpoint, and vision scoped to that model. Its regional rows are MiMo, OpenCode Go, and Custom.
Read Xiaomi's official MiMo developer introduction and OpenAI-compatible API documentation. Use the official catalog and, when supported by the selected endpoint, its authenticated GET /models response for served IDs. OpenCode Go is a gateway: query its authenticated GET https://opencode.ai/zen/go/v1/models separately. Do not infer vision from a name such as omni; verify image input on the exact model and route. Custom is user-supplied and has no provider-wide latest answer.
The native MiMo picker carries mimo-v2.5 and text-only mimo-v2.5-pro. The deprecated mimo-v2-pro and mimo-v2-omni entries are removed from native curation only. Native mimo-v2.5 retains the reviewed LingTai-side vision capability; no Go modality is inferred. OpenCode Go keeps its exact pre-PR picker — mimo-v2.5, mimo-v2.5-pro, mimo-v2-pro, and mimo-v2-omni — and prior behavior. No official MiMo vision MCP is established.
Start at mimoPreset in tui/internal/preset/preset.go. Revise providerModels["mimo"] and the matching modelHasVision entries in tui/internal/tui/preset_editor.go. Revise ProviderRegionURLs and ProviderDefaultEnv only for endpoint/credential behavior, and confirm the constructor's vision provider remains scoped to the intended model and route. Follow the latest-two-generation rule in tui/internal/tui/SKILL.md and tui/CONTRACT.md.
When an edited built-in is stamped a numbered key slot, the prefix is the provider name: MIMO_1_API_KEY, not the ProviderDefaultEnv slot XIAOMI_API_KEY. Keep this distinction when revising endpoint behavior.
test cases passed, vs 6 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.