Launchdarkly Flag Targeting

{
  "name": "launchdarkly-flag-targeting",
  "description": "Control LaunchDarkly feature flag targeting including toggling, rollouts, rules, individual targets, cross-environment copying, and approval workflows",
  "version": "1.0.0-experimental",
  "author": "LaunchDarkly",
  "repository": "https://github.com/launchdarkly/ai-tooling",
  "skills": ["./"],
  "tags": [
    "launchdarkly",
    "feature-flags",
    "feature-management",
    "targeting",
    "rollout",
    "percentage-rollout",
    "devops",
    "mcp"
  ],
  "requirements": {
    "mcp-servers": ["@launchdarkly/mcp-server"]
  }
}


# 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

- [LaunchDarkly Flag Create](../launchdarkly-flag-create/): Create flags before targeting them
- [LaunchDarkly Flag Discovery](../launchdarkly-flag-discovery/): Audit flags and understand the landscape
- [LaunchDarkly MCP Server](https://github.com/launchdarkly/mcp-server)
- [LaunchDarkly Docs](https://docs.launchdarkly.com)

## License

Apache-2.0


# Approval Workflows

Some LaunchDarkly environments require approval before changes take effect. This is an Enterprise feature configured per environment. When this happens, mutation tools like `toggle-flag`, `update-rollout`, `update-targeting-rules`, `update-individual-targets`, and `copy-flag-config` return `requiresApproval: true` instead of making the change directly.

## Detecting Approval Requirements

Any mutation tool response may include these fields when a change is blocked:

- `requiresApproval: true`: the change was blocked and needs approval
- `approvalUrl`: a URL where the approval can be reviewed (if available)
- `message`: a human-readable explanation
- `instructions`: the semantic patch instructions that were attempted (use these to create an approval request)

## Creating an Approval Request

When a change is blocked, use `create-approval-request` to submit the change for review:

1. Use the **same instructions** returned in the blocked response's `instructions` field
2. Provide a clear `description` explaining what the change does and why
3. Optionally notify specific team members (`notifyMemberIds`) or teams (`notifyTeamKeys`)

### Example: Toggle flag with approval

If `toggle-flag` returns `requiresApproval: true`:

```
Tool: create-approval-request
Input:
  projectKey: "my-project"
  flagKey: "new-checkout"
  env: "production"
  instructions: [{"kind": "turnFlagOn"}]
  description: "Enable new checkout flow in production