Update, retire, and delete LaunchDarkly configs and their variations. Use when you need to modify config properties, change model parameters, update instructions or messages, take unused configs out of service, or permanently remove them.
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
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.
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 parametersupdate-agent-config with resource: "targeting" -- turn a config's targeting off in an environment to take it out of serviceOptional MCP tools:
delete-agent-config with resource: "config" -- permanently delete a config (irreversible)delete-agent-config with resource: "variation" -- permanently delete a variation (irreversible)Start with get-agent-configs (configKey, section: "health") to get a structured health assessment. This detects:
The health verdict (healthy, warning, unhealthy) helps you prioritize what to fix.
Then use get-agent-configs to review the full detail:
To restore an earlier prompt or model, call get-agent-configs with section: "versions" and the variationKey to list that variation's saved versions, newest first, then pass the chosen version's model and messages to update-agent-config with resource: "variation".
Update config metadata -- Use update-agent-config with resource: "config":
defaultVariationKey (what new environments serve by default; existing environments keep their fallthrough, so change those with resource: "targeting")maintainerId or maintainerTeamKey (not both; an empty string removes it)Configs cannot be archived: the tool rejects archived.
Update a variation -- Use update-agent-config with resource: "variation" and the variationKey (requires confirm: true; pass it after the user agrees):
modelConfigKey and modelName)variationNametools arrayRetire a config -- Configs cannot be archived. To take one out of service but keep it recoverable, turn its targeting off with update-agent-config, resource: "targeting", the env, on: false, and confirm: true (pass it after the user agrees). This is the preferred way to retire a config:
on: true)get-agent-configs with section: "status" to see where the config is live, and ask which environments to turn off rather than guessingDelete -- Use delete-agent-config with resource: "config" or resource: "variation" (irreversible, requires confirm: true). Always suggest turning targeting off first. Only proceed with deletion if the user explicitly confirms they want permanent, irreversible removal.
Use get-agent-configs to confirm the response shows your updated values.
Report results:
archived -- configs cannot be archived and the tool rejects itget-agent-configs insteadTo learn more about creating and managing variations, read Create and manage config variations.
configs-variations -- Create variations to test changes side-by-sidetools -- Update tool attachmentslaunchdarkly/ai-tooling
26ae03b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.