preset-skill-op-availability-save-gate

Documents that preset editor Save performs structural validation only without live provider network calls.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It clarifies a common misconception about the LingTai TUI preset editor: saving a preset does not test whether the provider or model is actually reachable, so a successful save does not guarantee a working configuration.

Core Features & Use Cases

  • Save behavior contract: Explains that commit() in preset_editor.go runs only the preset's structural Validate() and saves immediately, with no HTTP probe, pending state, or credential fingerprinting gate.
  • Historical context: Records that a live availability gate on Save was removed on 2026-07-23 because it false-positived on transient network conditions for Codex, Codex-pool, and API-key providers like DeepSeek.
  • Correct diagnosis path: Points to /doctor (probeLLM in doctor.go) and real runtime execution as the places that diagnose actual provider/model reachability.
  • Use Case: When a user saves a preset successfully but the model fails at runtime, consult this Skill to understand that Save never checked availability and to route diagnosis to /doctor.

Quick Start

Ask whether saving a preset in the TUI verifies that the provider and model are actually reachable, and where live availability is checked instead.

Frequently Asked Questions about preset-skill-op-availability-save-gate

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

FAQPage Schema
Does saving a preset in the LingTai TUI test the provider connection?

No, saving a preset runs only the preset's structural Validate() and saves immediately. There is no live HTTP call, pending state, or credential check on Save for any provider, including Codex and API-key providers like DeepSeek.

How do I check if a provider or model is actually reachable in LingTai?

Use the /doctor command, whose probeLLM function in doctor.go diagnoses live provider and model reachability. Real runtime execution is the other place where actual availability surfaces.

Why did my preset save successfully but fail at runtime?

Save only validates the preset's structure, not live availability, so a structurally valid but unreachable provider still saves. Run /doctor or execute the configuration to diagnose the actual connectivity problem.

Why was the live availability check on preset Save removed?

The earlier gate made a real provider call on every Save and blocked saving on non-2xx responses, but it false-positived on transient network conditions for working configurations. It was removed on 2026-07-23 and not replaced.

What does preset Validate() check before saving?

Validate() performs structural checks on the preset only, as documented in the saved-presets operations reference. It does not probe network endpoints or fingerprint credentials.