From launchdarkly
Updates, archives, and deletes LaunchDarkly AI configs and variations. Use to modify config properties, change model parameters, update instructions, or retire configs via reversible archival.
How this skill is triggered — by the user, by Claude, or both
Slash command
/launchdarkly:configs-updateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You're using a skill that will guide you through updating, archiving, and deleting configs and their variations. Your job is to understand the current state of the config, make the changes, and verify the result.
You're using a skill that will guide you through updating, archiving, 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-ai-config-health -- assess config health before making changes (detects missing models, orphaned tools, empty configs)get-ai-config -- understand current state before making changesupdate-ai-config -- update config metadata (name, description, tags, archive)update-ai-config-variation -- update variation model, prompts, or parametersOptional MCP tools:
delete-ai-config -- permanently delete a config (irreversible)delete-ai-config-variation -- permanently delete a variation (irreversible)Start with get-ai-config-health to get a structured health assessment. This detects:
The health verdict (healthy, warning, unhealthy) helps you prioritize what to fix.
Then use get-ai-config to review the full detail:
Update config metadata -- Use update-ai-config:
archived: true (reversible)Update a variation -- Use update-ai-config-variation:
modelConfigKey and modelName)Archive a config -- Use update-ai-config with archived: true. Archiving is the preferred way to retire a config:
archived: false)Delete -- Use delete-ai-config or 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.
Use get-ai-config to confirm the response shows your updated values.
Report results:
get-ai-config insteadconfigs-variations -- Create variations to test changes side-by-sidetools -- Update tool attachmentsnpx claudepluginhub launchdarkly/ai-tooling --plugin launchdarklyCreates and configures LaunchDarkly AI configs, guiding mode selection (agent vs completion), variation creation with models/prompts, and setup verification.
Automates LaunchDarkly feature flag, environment, segment, and rollout management via Rube MCP (Composio). Always searches tools first for current schemas.
Creates a feature flag management guide and lifecycle playbook covering taxonomy, rollout, monitoring, cleanup, and governance for a service or team.