Skill Claude CodeCodex
Use when revising the built-in codex TUI preset.
LingTai AI
This repository also configures its own agents. See what lingtai tells them →
Skill Claude CodeCodex
Use when revising the built-in codex TUI preset.
Skill Claude CodeCodex
Use when revising the built-in custom TUI preset.
Skill Claude CodeCodex
Use when revising the built-in deepseek TUI preset.
Skill Claude CodeCodex
Use when revising the built-in gemini TUI preset.
Skill Claude CodeCodex
Use when revising the built-in grok TUI preset.
Skill Claude CodeCodex
Use when revising the built-in kimi TUI preset.
Skill Claude CodeCodex
Use when revising the built-in mimo TUI preset.
Skill Claude CodeCodex
Use when revising the built-in minimax TUI preset.
Skill Claude CodeCodex
Use when revising the built-in nvidia TUI preset.
Skill Claude CodeCodex
Use when revising the built-in openrouter TUI preset.
Skill Claude CodeCodex
How a saved preset becomes the running default, first-run/setup choice semantics, propagation, and what /refresh actually switches.
Skill Claude CodeCodex
Save on the preset editor performs local structural validation only — it never makes a live provider/model network call. Real availability diagnosis is owned by /doctor and actual runtime execution.
Skill Claude CodeCodex
Base URL / API-compat / provider / model / capability declaration shape versus credentials and live probes; includes proven Codex OAuth quota inspection with exact agent query routing and dated official-vs-measured context-window evidence.
Skill Claude CodeCodex
How saved presets differ from templates, and the Load/Save/Delete/Bootstrap contract — order, atomicity, and naming.
Skill Claude CodeCodex
Bounded first-pass triage for preset problems; routes deeper runtime/update/migration questions elsewhere instead of guessing.
Skill Claude CodeCodex
Use when revising the built-in zhipu TUI preset.
Skill Claude CodeCodex
Menu manual (not a tool) for recipes — the named payload that shapes an orchestrator's greeting, ongoing behaviour, and shipped library; every LingTai project uses one. Routes to reference/recipe-format/SKILL.md (authoring/customising) and reference/export-recipe/SKILL.md (publishing for new networks), and warns about…
Skill Claude CodeCodex
Nested lingtai-recipe reference for exporting a standalone recipe bundle from a live network or methodology: scope disambiguation, human-in-the-loop metadata collection, bundle authoring, validation, git initialization, and handoff.
Skill Claude CodeCodex
Nested lingtai-recipe reference for authoring and validating recipe bundles: bundle structure, .recipe/recipe.json schema, behavioral layers, library sibling mechanics, locale fallback, validator checks, hand-authored recipes, testing, and publishing.
Skill Claude CodeCodex
Source-navigation guide for the LingTai Go monorepo that ships lingtai-tui and lingtai-portal. Read this for TUI/Portal structure, runtime-boundary evidence, exact Go ownership, or when updating an ANATOMY.md. The repository-root ANATOMY.md is normative; this skill routes into that graph without duplicating it. Kernel…
Skill Claude CodeCodex
Anything you need to know about LingTai TUI. Read this first for the stable mental model, feature map, interface/slash-command help, or the right source/manual route for a TUI question. Exact command prose lives in the localized help assets, Go structure lives in lingtai-tui-anatomy, and presets, Portal, tutorials…
Skill Claude CodeCodex
The 12-lesson curriculum for teaching a human how LingTai works — orientation, agent runtime, communication, memory/molt, capabilities, operations, addons, and graduation. Invoke this skill when the human is ready to begin or continue the tutorial.
Skill Claude CodeCodex
Nested tutorial-guide reference for lessons 4–6: init.json, lingtai-agent run, heartbeat and signal files, TUI runtime wrapping, and system prompt identity.
Skill Claude CodeCodex
Nested tutorial-guide reference for lesson 9: avatars, network exercises, and dynamic capability demonstrations.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: