Config Update & Lifecycle

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

Prerequisites

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

Required MCP tools:

• get-agent-configs with configKey -- understand current state before making changes; add section: "health" to assess config health (detects missing models, orphaned tools, empty configs)
• update-agent-config with resource: "config" -- update config metadata (name, description, tags, default variation, maintainer)
• update-agent-config with resource: "variation" -- update variation model, prompts, or parameters
• update-agent-config with resource: "targeting" -- turn a config's targeting off in an environment to take it out of service

Optional MCP tools:

• delete-agent-config with resource: "config" -- permanently delete a config (irreversible)
• delete-agent-config with resource: "variation" -- permanently delete a variation (irreversible)

Core Principles