configs-update

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

AI Config Update & Lifecycle

AI Config 更新与生命周期

You're using a skill that will guide you through updating, archiving, and deleting AI Configs and their variations. Your job is to understand the current state of the config, make the changes, and verify the result.

您正在使用一项技能，它将引导您完成AI Config及其变体的更新、归档和删除操作。您的任务是了解配置的当前状态、进行更改并验证结果。

Prerequisites

前提条件

This skill requires the remotely hosted LaunchDarkly MCP server to be configured in your environment.

Required MCP tools:

```
get-ai-config-health
```
-- assess config health before making changes (detects missing models, orphaned tools, empty configs)
```
get-ai-config
```
-- understand current state before making changes
```
update-ai-config
```
-- update config metadata (name, description, tags, archive)
```
update-ai-config-variation
```
-- update variation model, prompts, or parameters

Optional MCP tools:

```
delete-ai-config
```
-- permanently delete a config (irreversible)
```
delete-ai-config-variation
```
-- permanently delete a variation (irreversible)

本技能要求您的环境中已配置远程托管的LaunchDarkly MCP服务器。

必需的MCP工具：

```
get-ai-config-health
```
—— 在进行更改前评估配置健康状况（检测缺失的模型、孤立的工具、空配置）
```
get-ai-config
```
—— 在进行更改前了解当前状态
```
update-ai-config
```
—— 更新配置元数据（名称、描述、标签、归档状态）
```
update-ai-config-variation
```
—— 更新变体的模型、提示词或参数

可选的MCP工具：

```
delete-ai-config
```
—— 永久删除配置（不可撤销）
```
delete-ai-config-variation
```
—— 永久删除变体（不可撤销）

Core Principles

核心原则

Fetch Before Changing: Always check the current state before modifying
Verify After Changing: Fetch the config again to confirm updates were applied
Archive Before Deleting: Archival is reversible; deletion is not

更改前获取状态：修改前务必检查当前状态
更改后验证：再次获取配置以确认更新已生效
删除前先归档：归档是可撤销的；删除则不可撤销

Workflow

工作流程

Step 1: Assess Health and Understand Current State

步骤1：评估健康状况并了解当前状态

Start with

get-ai-config-health

to get a structured health assessment. This detects:

Variations with no model (show as "NO MODEL" in the UI)
Variations with neither instructions nor messages
Orphaned tool references (tools attached that don't exist in the project)
Configs with no variations at all

The health verdict (

healthy

warning

unhealthy

) helps you prioritize what to fix.

Then use

get-ai-config

to review the full detail:

Current mode (agent or completion)
Existing variations and their models
Current instructions or messages
Attached tools and parameters

首先使用

get-ai-config-health

获取结构化的健康评估结果。它会检测：

无模型的变体（在UI中显示为"NO MODEL"）
既无指令也无消息的变体
孤立的工具引用（附加的工具在项目中不存在）
完全没有变体的配置

健康判定结果（

healthy

、

warning

、

unhealthy

）有助于您确定需要优先修复的内容。

然后使用

get-ai-config

查看完整详情：

当前模式（agent或completion）
现有变体及其模型
当前指令或消息
附加的工具和参数

Step 2: Make the Update

步骤2：执行更新

Update config metadata -- Use

update-ai-config

Change name or description
Add or replace tags
Archive with
```
archived: true
```
(reversible)

Update a variation -- Use

update-ai-config-variation

Switch model (provide new
```
modelConfigKey
```
and
```
modelName
```
)
Change instructions or messages
Tune parameters (temperature, max_tokens, etc.)
Attach or detach tools via the parameters object

Archive a config -- Use

update-ai-config

with

archived: true

. Archiving is the preferred way to retire a config:

It is reversible (unarchive with
```
archived: false
```
)
The config is hidden from active lists but preserved
After calling the archive, treat a successful response as confirmation and proceed to verification
When a user says "remove", "retire", "decommission", or "no longer need", default to archiving unless they explicitly say "delete permanently"

Delete -- Use

delete-ai-config

delete-ai-config-variation

(irreversible, requires

confirm: true

). Always suggest archiving first. Only proceed with deletion if the user explicitly confirms they want permanent, irreversible removal.

更新配置元数据 —— 使用

update-ai-config

：

修改名称或描述
添加或替换标签
设置
```
archived: true
```
进行归档（可撤销）

更新变体 —— 使用

update-ai-config-variation

：

切换模型（提供新的
```
modelConfigKey
```
和
```
modelName
```
）
修改指令或消息
调整参数（temperature、max_tokens等）
通过parameters对象附加或分离工具

归档配置 —— 使用

update-ai-config

并设置

archived: true

。归档是停用配置的首选方式：

可撤销（设置
```
archived: false
```
即可取消归档）
配置会从活跃列表中隐藏，但会被保留
调用归档后，将成功响应视为确认，然后进行验证步骤
当用户说"移除"、"停用"、"退役"或"不再需要"时，默认选择归档，除非用户明确表示"永久删除"

删除 —— 使用

delete-ai-config

或

delete-ai-config-variation

（不可撤销，需要

confirm: true

）。始终建议先归档。只有当用户明确确认需要永久、不可撤销的删除时，才执行删除操作。

Step 3: Verify

步骤3：验证

Use

get-ai-config

to confirm the response shows your updated values.

Report results:

Update applied successfully
Config reflects changes
Flag any issues or rollback if needed

使用

get-ai-config

确认响应显示您所做的更新值。

报告结果：

更新已成功应用
配置已反映更改
标记任何问题，如有需要进行回滚

What NOT to Do

禁止操作

Don't update production configs without testing in another variation first
Don't change multiple things at once -- make incremental changes
Don't skip verification
Don't delete without explicit user confirmation -- always suggest archiving first
Don't retry an update because the API response doesn't echo back the exact values you sent -- verify with
```
get-ai-config
```
instead

不要在未先在其他变体中测试的情况下更新生产环境配置
不要同时更改多项内容——进行增量式更改
不要跳过验证步骤
不要在未获得用户明确确认的情况下进行删除——始终先建议归档
不要因为API响应未回显您发送的确切值而重试更新——改用
```
get-ai-config
```
进行验证