LaunchDarkly's public collection of AI agent skills and playbooks. These skills encode repeatable workflows for working with LaunchDarkly, so coding agents can execute common tasks safely and consistently.
Agent Skills are modular, text-based playbooks that teach an agent how to perform a workflow. This repo is designed to be a public, open-source home for LaunchDarkly skills and to align with the emerging Agent Skills Open Standard.
| Skill | Description |
|---|---|
feature-flags/launchdarkly-flag-discovery |
Audit flags, find stale/launched flags, and assess removal readiness |
feature-flags/launchdarkly-flag-create |
Create new feature flags in a way that fits existing codebase patterns |
feature-flags/launchdarkly-flag-targeting |
Control targeting, rollouts, rules, and cross-environment config |
feature-flags/launchdarkly-flag-cleanup |
Safely remove flags from code using LaunchDarkly as the source of truth |
feature-flags/launchdarkly-guarded-rollout |
Configure guarded rollouts with progressive traffic, metric monitoring, and rollback |
| Skill | Description |
|---|---|
ai-configs/aiconfig-create |
Create AI Configs with variations for agent or completion mode |
ai-configs/aiconfig-migrate |
Migrate an app with hardcoded LLM prompts to AI Configs in five stages (extract, wrap, tools, tracking, evals) |
ai-configs/aiconfig-update |
Update and delete AI Configs, manage lifecycle |
ai-configs/aiconfig-variations |
Manage AI Config variations for A/B testing |
ai-configs/aiconfig-tools |
Create and attach tools for function calling |
ai-configs/aiconfig-projects |
Create and manage projects to organize AI Configs |
ai-configs/aiconfig-online-evals |
Attach LLM-as-a-judge evaluators to AI Configs |
ai-configs/aiconfig-targeting |
Configure targeting rules for AI Config rollouts |
ai-configs/aiconfig-snippets |
Create and manage reusable prompt snippets across AI Configs |
ai-configs/aiconfig-agent-graphs |
Create and manage multi-agent graphs with routing and handoffs |
| Skill | Description |
|---|---|
experiments/launchdarkly-experiment-setup |
Set up experiments with metrics, treatments, and data collection |
| Skill | Description |
|---|---|
metrics/launchdarkly-metric-choose |
Select the right metric type for an experiment |
metrics/launchdarkly-metric-create |
Create metrics and instrument tracking events |
metrics/launchdarkly-metric-instrument |
Add tracking calls to code for existing metrics |
This repo is a Claude Code plugin. Installing it gives you all the skills above plus the LaunchDarkly MCP server.
- Open Claude Code and run
/plugin install. - Search for LaunchDarkly, or install directly from the repo URL:
https://github.com/launchdarkly/ai-tooling - Authenticate the LaunchDarkly MCP server when prompted with your API access token.
Once installed, skills are available as /launchdarkly:<skill-name> across all your projects, and the MCP server can read and modify your flags directly.
| Skill | Description |
|---|---|
onboarding |
End-to-end LaunchDarkly setup: kickoff roadmap, MCP, SDK install, first flag |
onboarding/mcp-configure |
Configure the LaunchDarkly hosted MCP server (OAuth, no API keys needed) |
onboarding/sdk-install |
Install and initialize the correct SDK via detect, plan, and apply sub-steps |
onboarding/first-flag |
Create a boolean flag, evaluate it, toggle on/off for end-to-end proof |
This repo is a Cursor plugin. Installing it gives you all the skills above plus the LaunchDarkly MCP server, so the agent can read and modify your flags directly.
- Open Cursor and go to Settings > Plugins.
- Search for LaunchDarkly in the marketplace, or install from the repo URL:
https://github.com/launchdarkly/ai-tooling
Once installed, the skills and MCP server are available across all your projects.
# Clone the repo
git clone https://github.com/launchdarkly/ai-tooling.git
cd ai-tooling
# If your agent supports skills.sh installs:
npx skills add launchdarkly/ai-tooling
# Or manually copy a skill into your agent's skills path:
cp -r skills/feature-flags/launchdarkly-flag-cleanup <your-agent-skills-dir>/
Then ask your agent something like:
Which feature flags are stale and should be cleaned up?
Create a feature flag for the new checkout flow
Roll out dark-mode to 25% of users in production
Remove the `new-checkout-flow` feature flag from this codebase
npx skills add <owner/repo>See CONTRIBUTING.md for how to add new skills and the conventions we follow.
Apache-2.0