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

/launchdarkly-flag-targeting

@f0ee110 official
Run it yourself

Control LaunchDarkly feature flag targeting including toggling flags on/off, percentage rollouts, targeting rules, individual targets, and copying flag configurations between environments. Use when the user wants to change who sees a flag, roll out to a percentage, add targeting rules, or promote config between environments.

Use this Skill: https://skilld.dev/gh/launchdarkly/ai-tooling/launchdarkly-flag-targeting

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

README.md

≈491 tokens on demand. Your agent reads this file only when SKILL.md points to it.

LaunchDarkly Flag Targeting Skill

An Agent Skill for controlling feature flag targeting, rollouts, and rules in LaunchDarkly.

Overview

This skill teaches agents how to:

  • Understand current flag targeting state before making changes
  • Toggle flags on/off safely
  • Set up percentage rollouts
  • Add and manage targeting rules
  • Manage individual user/context targets
  • Copy targeting config between environments
  • Follow safety practices for production changes

Installation (Local)

For now, install by placing this skill directory where your agent client loads skills.

Examples:

  • Generic: copy skills/feature-flags/launchdarkly-flag-targeting/ into your client's skills path

Prerequisites

This skill requires the remotely hosted LaunchDarkly MCP server to be configured in your environment. The remote server provides higher-level, agent-optimized tools that orchestrate multiple API calls and return pruned, actionable responses.

Refer to your LaunchDarkly account settings for instructions on connecting to the remotely hosted MCP server.

Usage

Once installed, the skill activates automatically when you ask about flag targeting:

Turn on the new-checkout flag in staging
Roll out dark-mode to 25% of users in production
Target beta users for the new-pricing feature
Copy the staging config for checkout-v2 to production

Structure

launchdarkly-flag-targeting/
├── SKILL.md
├── marketplace.json
├── README.md
└── references/
    ├── targeting-patterns.md
    └── safety-checklist.md

Related

License

Apache-2.0

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 alerts2d3 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    This skill provides a comprehensive and safe interface for managing LaunchDarkly feature flags, with built-in safety checks and adherence to organizational approval workflows.

  • Socket2d

    No alerts

  • Snyk2d

    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 days ago
compatibility
Requires the remotely hosted LaunchDarkly MCP server
metadata
{
  "author": "launchdarkly",
  "version": "1.1.1-experimental"
}
  • launchdarkly
  • feature-flags
  • targeting
  • rollouts
  • rules
  • mcp-server
  • approval-workflows

README badge

README badge for launchdarkly/ai-tooling/launchdarkly-flag-targeting

Manages LaunchDarkly feature flag targeting including toggling flags on/off, setting percentage rollouts, adding targeting rules, and copying configurations between environments. Use when you need to control flag visibility, stage a rollout, add audience rules, or promote flag settings from one environment to another.

Generated from the current SKILL.md.

Does this skill work without the LaunchDarkly MCP server?
No. This skill requires the remotely hosted LaunchDarkly MCP server to be configured in your environment to use any of the targeting tools.
Can I copy flag configuration between environments?
Yes. The optional `copy-flag-config` tool lets you promote targeting configuration from one environment (like staging) to another (like production).
What happens if I toggle a flag on when it has targeting rules configured?
The flag will begin evaluating its targeting rules and individual targets. If nothing matches, it falls back to the default rule (fallthrough) variation or percentage rollout.
Do I need approval to make flag changes?
Some environments require approval workflows. If a change is blocked, the skill will create an approval request and prompt you to share it for review before the change can be applied.
What takes priority: individual targets, rules, or the default rollout?
Individual targets are highest priority and override all rules. Custom targeting rules are evaluated next, top-to-bottom. The default rule (fallthrough) applies only if nothing else matches.

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