Index of every page on this site: llms.txt
All skills
launchdarkly avatar

/configs-update

@f0ee110 official
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/launchdarkly/ai-tooling/configs-update

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈64 tokens for metadata: the name and description. ≈1.4k when used: this file. ≈338 more on demand in 1 file.

Description uses 3.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈255 characters, or 3.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

  1. Fetch Before Changing: Always check the current state before modifying
  2. Verify After Changing: Fetch the config again to confirm updates were applied
  3. Turn Off Before Deleting: Configs cannot be archived. Turning targeting off is reversible; deletion is not

Workflow

Step 1: Assess Health and Understand Current State

Start with get-agent-configs (configKey, section: "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-agent-configs to review the full detail:

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

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".

Step 2: Make the Update

Update config metadata -- Use update-agent-config with resource: "config":

  • Change name or description
  • Add or replace tags
  • Set defaultVariationKey (what new environments serve by default; existing environments keep their fallthrough, so change those with resource: "targeting")
  • Set the maintainer with 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):

  • Switch model (provide new modelConfigKey and modelName)
  • Rename it with variationName
  • Change instructions or messages
  • Tune parameters (temperature, max_tokens, etc.)
  • Attach or detach tools with the top-level tools array

Retire 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:

  • It is reversible (turn targeting back on with on: true)
  • The config, its variations, and their version history are preserved
  • It is per environment: check get-agent-configs with section: "status" to see where the config is live, and ask which environments to turn off rather than guessing
  • When a user says "remove", "retire", "decommission", or "no longer need", default to turning targeting off unless they explicitly say "delete permanently"

Delete -- 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.

Step 3: Verify

Use get-agent-configs to confirm the response shows your updated values.

Report results:

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

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 turning targeting off first
  • Don't pass archived -- configs cannot be archived and the tool rejects it
  • Don't retry an update because the API response doesn't echo back the exact values you sent -- verify with get-agent-configs instead

More resources

To learn more about creating and managing variations, read Create and manage config variations.

Related Skills

  • configs-variations -- Create variations to test changes side-by-side
  • tools -- Update tool attachments

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts11d3 checks · Risk SAFE
  • Gen Agent Trust Hub15d

    This skill is safe. It enables agents to manage LaunchDarkly AI configurations through official MCP tools. It implements strong safety practices, including mandatory user confirmation for destructive actions, verification of changes, and suggesting reversible alternatives to permanent deletion. All external resources belong to the official vendor.

  • Socket11d

    No alerts

  • Snyk15d

    Risk: LOW · No issues

Signed by skilld at f0ee110. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago
compatibility
Requires the remotely hosted LaunchDarkly MCP server
metadata
{
  "author": "launchdarkly",
  "version": "1.0.0-experimental"
}
  • MCP
  • launchdarkly
  • config-management
  • ai-models
  • lifecycle
  • variations
  • archival

README badge

README badge for launchdarkly/ai-tooling/configs-update

Modifies, archives, and deletes LaunchDarkly AI configs and their variations through the LaunchDarkly MCP server. Use this skill to update config metadata, change model parameters, swap instructions or messages, or retire configs—with built-in health checks and verification steps to catch orphaned tools and missing models before publishing changes.

Generated from the current SKILL.md.

What's the difference between archiving and deleting a config?
Archiving is reversible and hides the config from active lists while preserving it; deletion is permanent and irreversible. Always suggest archiving unless the user explicitly requests permanent removal.
Does this skill require any setup?
Yes. It requires the remotely hosted LaunchDarkly MCP server to be configured in your environment with the required MCP tools (get-ai-config-health, get-ai-config, update-ai-config, update-ai-config-variation).
Can I update multiple config properties at once?
No. The skill guidance is to make incremental changes and verify each one rather than batching updates together.
What should I check before making changes?
Always run get-ai-config-health first to assess the config's current state and detect issues like missing models, orphaned tool references, or empty configs. Then use get-ai-config to review full details before modifying.

Generated from the current SKILL.md. These answers refresh after source changes.