preset-skill-op-troubleshooting-migration

Triages preset problems and routes runtime, update, and migration questions to owning skills.

692|60|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Lingtai-AI/lingtai --skill preset-skill-op-troubleshooting-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preset-skill-op-troubleshooting-migration
Source: https://github.com/Lingtai-AI/lingtai/tree/main/tui/internal/preset/skills/lingtai-preset-skill/reference/operations/troubleshooting-migration
Command: npx skills add https://github.com/Lingtai-AI/lingtai --skill preset-skill-op-troubleshooting-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a LingTai TUI preset misbehaves, it is hard to know whether the cause is a preset-package issue, a kernel runtime issue, or a migration concern. This Skill provides bounded first-pass triage for a fixed set of preset symptoms and explicitly routes everything else to the correctly owned skill or source location instead of guessing.

Core Features & Use Cases

  • Symptom-to-cause mapping: Explains five known preset symptoms, such as saved presets not updating after a TUI upgrade, retired templates disappearing, and saves failing due to structural Validate() rejection.
  • Explicit routing boundaries: Directs runtime, update/upgrade mechanics, and live provider failures to kernel-side skills, the migration package's ANATOMY.md, or /doctor rather than speculating.
  • Use Case: A user reports their saved preset did not change after upgrading the TUI. The Skill explains that RefreshTemplates only rewrites templates/ and never saved/, and points to the saved-presets reference for re-creating the preset from the refreshed template.

Quick Start

Ask why a saved preset did not update after a TUI upgrade and follow the triage guidance to the correct owning reference.

Frequently Asked Questions about preset-skill-op-troubleshooting-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why didn't my saved preset update after a TUI upgrade?

Saved presets not updating after an upgrade is expected behavior. RefreshTemplates only rewrites the templates/ directory and never touches saved/. To get the new template's changes, re-create the saved preset from the refreshed template.

Why did a preset template I used before disappear?

A missing template was likely pruned by RefreshTemplates because it is no longer in BuiltinPresets(), meaning it was retired. A saved clone of a retired template is untouched and still loads normally.

Why does saving a preset fail or appear stuck?

Save no longer runs a live provider check, so there is no pending or blocked save state. A save failure means the structural Validate() rejected the preset or a file-write error occurred; provider availability is a /doctor question instead.

Why doesn't editing the preset file change the running agent?

Editing the preset or pool file does not affect a running session because saving alone never switches an active agent. An explicit refresh, relaunch, or new service construction is required for changes to take effect.

What preset problems are out of scope for this troubleshooting skill?

Kernel runtime internals, TUI update and migration mechanics, and live provider request failures are out of scope. These route to kernel-side skills, the migration package's ANATOMY.md, or /doctor rather than being diagnosed from preset-package evidence.