LaunchDarkly Automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/launch-darkly-automation --openclawLaunchDarkly Automation
Automate your LaunchDarkly feature flag workflows -- enumerate projects and environments, create webhook-driven flag triggers, manage trigger lifecycle, and audit code references across repositories.
Toolkit docs: composio.dev/toolkits/launch_darkly
Setup
- Add the Composio MCP server to your client:
https://rube.app/mcp - Connect your LaunchDarkly account when prompted (API key authentication)
- Start using the workflows below
Core Workflows
1. List Projects
Use LAUNCH_DARKLY_LIST_PROJECTS to discover all projects and their keys for subsequent operations.
Tool: LAUNCH_DARKLY_LIST_PROJECTS
Inputs:
- filter: string (e.g., "query:myproject" or "keys:proj1,proj2" or "tags:mytag")
- expand: string (e.g., "environments" to include env list per project)
- limit: integer (default 20)
- offset: integer (pagination start index)
- sort: string (e.g., "name" or "-name" for descending)
2. Get Environments for a Project
Use LAUNCH_DARKLY_GET_ENVIRONMENTS to list all environments within a project (production, staging, test, etc.).
Tool: LAUNCH_DARKLY_GET_ENVIRONMENTS
Inputs:
- project_key: string (required) -- e.g., "my-project", "default"
- filter: string (e.g., "query:production")
- limit: integer (default 20)
- offset: integer (pagination)
- sort: string (e.g., "name" or "-name")
3. Create a Flag Trigger Workflow
Use LAUNCH_DARKLY_CREATE_TRIGGER_WORKFLOW to set up automated flag toggles triggered by external events (webhooks, Datadog alerts, etc.).
Tool: LAUNCH_DARKLY_CREATE_TRIGGER_WORKFLOW
Inputs:
- project_key: string (required)
- feature_flag_key: string (required) -- e.g., "new-feature", "enable-dark-mode"
- environment_key: string (required) -- e.g., "production", "staging"
- integration_key: string (default "generic-trigger") -- or "datadog", "honeycomb", "dynatrace"
- instructions: array of objects (optional):
- kind: "flag_action" (fixed)
- action: "turnFlagOn" | "turnFlagOff"
- comment: string (optional) -- description of the trigger purpose
The trigger generates a unique webhook URL that can be called to execute the configured flag action.
4. Delete a Flag Trigger Workflow
Use LAUNCH_DARKLY_DELETE_TRIGGER_WORKFLOW to permanently remove a trigger and its URL.
Tool: LAUNCH_DARKLY_DELETE_TRIGGER_WORKFLOW
Inputs:
- project_key: string (required)
- feature_flag_key: string (required)
- environment_key: string (required)
- id: string (required) -- the trigger ID returned during creation
Warning: Deletion is irreversible. The trigger and its URL cannot be recovered.
5. List Code Reference Repositories
Use LAUNCH_DARKLY_LIST_CODE_REFERENCE_REPOSITORIES to track where feature flags are used in your codebase.
Tool: LAUNCH_DARKLY_LIST_CODE_REFERENCE_REPOSITORIES
Inputs:
- projKey: string (optional) -- filter by project key
- flagKey: string (optional) -- filter by feature flag key
- withBranches: string (any value to include branch data)
- withReferencesForDefaultBranch: string (any value to include code refs for default branch)
Note: Code references is an Enterprise feature requiring code-reference-repository write permissions.
Known Pitfalls
| Pitfall | Detail |
|---|---|
| Project key discovery | Always use LAUNCH_DARKLY_LIST_PROJECTS first to find valid project keys before calling other tools. |
| Environment key format | Environment keys are lowercase slugs (e.g., "production", "test"), not display names. |
| Trigger deletion is permanent | Once deleted via LAUNCH_DARKLY_DELETE_TRIGGER_WORKFLOW, the trigger URL is unrecoverable. |
| Enterprise-only code refs | LAUNCH_DARKLY_LIST_CODE_REFERENCE_REPOSITORIES requires Enterprise plan and write permissions. |
| Trigger instructions format | Each instruction object requires kind: "flag_action" (fixed constant) and action as either turnFlagOn or turnFlagOff. |
Quick Reference
| Tool Slug | Description |
|---|---|
LAUNCH_DARKLY_LIST_PROJECTS | List all projects with filtering and pagination |
LAUNCH_DARKLY_GET_ENVIRONMENTS | List environments within a project |
LAUNCH_DARKLY_CREATE_TRIGGER_WORKFLOW | Create a webhook-driven flag trigger |
LAUNCH_DARKLY_DELETE_TRIGGER_WORKFLOW | Permanently delete a flag trigger |
LAUNCH_DARKLY_LIST_CODE_REFERENCE_REPOSITORIES | List repos with code references to flags |
Powered by Composio
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/launch-darkly-automation/SKILL.mdView on GitHub Overview
Automate LaunchDarkly feature flag workflows end-to-end. Enumerate projects and environments, create webhook-driven flag triggers, manage trigger lifecycles, and audit code references across repositories via the Composio MCP integration. This reduces manual steps and ensures consistent flag behavior across your deployments.
How This Skill Works
Connect the Composio MCP server to LaunchDarkly and expose a set of tooling commands. Use the provided tools (e.g., LAUNCH_DARKLY_LIST_PROJECTS, LAUNCH_DARKLY_GET_ENVIRONMENTS, LAUNCH_DARKLY_CREATE_TRIGGER_WORKFLOW, LAUNCH_DARKLY_DELETE_TRIGGER_WORKFLOW, LAUNCH_DARKLY_LIST_CODE_REFERENCE_REPOSITORIES) to perform operations and manage webhook-driven triggers. Triggers return a unique webhook URL that can be invoked to turn flags on or off.
When to Use It
- Onboard a new LD project and fetch its keys using LAUNCH_DARKLY_LIST_PROJECTS.
- Identify environments for a project with LAUNCH_DARKLY_GET_ENVIRONMENTS to prepare gating rules.
- Automate a feature flag toggle by creating a trigger workflow with LAUNCH_DARKLY_CREATE_TRIGGER_WORKFLOW.
- Decommission a trigger by deleting it with LAUNCH_DARKLY_DELETE_TRIGGER_WORKFLOW when no longer needed.
- Audit flag usage across codebases by listing code-reference repositories with LAUNCH_DARKLY_LIST_CODE_REFERENCE_REPOSITORIES.
Quick Start
- Step 1: Setup MCP and connect LaunchDarkly at https://rube.app/mcp.
- Step 2: Run LAUNCH_DARKLY_LIST_PROJECTS to discover projects and pick keys.
- Step 3: Create a trigger with LAUNCH_DARKLY_CREATE_TRIGGER_WORKFLOW using required fields and test the webhook URL.
Best Practices
- Always list projects first to validate keys before actions.
- Use explicit project_key and environment_key values; respect lowercase slug conventions.
- Provide a descriptive comment for triggers to clarify purpose.
- Secure trigger URLs and rotate integration keys according to policy.
- Regularly reconcile code references with LD flags to prevent drift.
Example Use Cases
- Onboarding: List all projects and environments, then prepare a trigger workflow for a new feature flag rollout.
- Incident response: Create a trigger that turns a flag on in production when an external alert fires.
- Deployment cleanup: Delete unused trigger workflows and revoke their URLs after releases.
- Code reference audit: List repositories to locate where a flag is used and plan refactors.
- Governance: Expand a project to include environment details for compliance reviews.