# Preset Skill Mimo

> Use when revising the built-in mimo TUI preset.

- Skill: `lingtai-ai/preset-skill-mimo` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lingtai-ai/preset-skill-mimo`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lingtai-ai/preset-skill-mimo/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lingtai-ai (https://skillmd.com/u/lingtai-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lingtai-ai/preset-skill-mimo

---


# mimo preset revision

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.

## Template-specific settings

Read Xiaomi's official [MiMo developer introduction](https://platform.xiaomimimo.com/llms.txt)
and [OpenAI-compatible API documentation](https://platform.xiaomimimo.com/docs/zh-CN/api/chat/openai-api).
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.

## TUI surfaces to revise

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.

## Reviewed deterministic revision

Prepare an evidence-bound manifest and explicit input, then run
lingtai-tui presets revise --manifest PATH --input PATH --mode dry-run|check|apply
[--output-dir PATH]. Review the JSON plan and diagnostics, use dry-run/check
before apply, and apply only to a new explicit output directory. revision.go
validates hashes, route bindings, and evidence and preserves unowned bytes. This
amendment narrows native curation while preserving the OpenCode Go list and
endpoint, credential, and capability behavior.

Maintenance: If the relevant TUI preset/page is revised, check whether this sub-skill also needs revision and, if so, include it in the same PR.

## Operations

For save, endpoint/capability, availability, activation/refresh, or
troubleshooting, use the five shared operation children under
`reference/operations/`; this child owns MiMo route, model, and vision facts.