LaunchDarkly Automation

Automate LaunchDarkly feature flag management -- list projects and environments, create and delete trigger workflows, and track code references via the Composio MCP integration.

23 stars

Best use case

LaunchDarkly Automation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Automate LaunchDarkly feature flag management -- list projects and environments, create and delete trigger workflows, and track code references via the Composio MCP integration.

Teams using LaunchDarkly Automation should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/launch-darkly-automation/SKILL.md --create-dirs "https://raw.githubusercontent.com/christophacham/agent-skills-library/main/skills/automation/launch-darkly-automation/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/launch-darkly-automation/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How LaunchDarkly Automation Compares

Feature / AgentLaunchDarkly AutomationStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Automate LaunchDarkly feature flag management -- list projects and environments, create and delete trigger workflows, and track code references via the Composio MCP integration.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# LaunchDarkly 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](https://composio.dev/toolkits/launch_darkly)

---

## Setup

1. Add the Composio MCP server to your client: `https://rube.app/mcp`
2. Connect your LaunchDarkly account when prompted (API key authentication)
3. 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](https://composio.dev)*

Related Skills

serpapi-automation

23
from christophacham/agent-skills-library

Automate Serpapi tasks via Rube MCP (Composio). Always search tools first for current schemas.

scrapingbee-automation

23
from christophacham/agent-skills-library

Automate Scrapingbee tasks via Rube MCP (Composio). Always search tools first for current schemas.

scrapingant-automation

23
from christophacham/agent-skills-library

Automate Scrapingant tasks via Rube MCP (Composio). Always search tools first for current schemas.

pdf-api-io-automation

23
from christophacham/agent-skills-library

Automate PDF API IO tasks via Rube MCP (Composio). Always search tools first for current schemas.

openweather-api-automation

23
from christophacham/agent-skills-library

Automate Openweather API tasks via Rube MCP (Composio). Always search tools first for current schemas.

onesignal-rest-api-automation

23
from christophacham/agent-skills-library

Automate OneSignal tasks via Rube MCP (Composio): push notifications, segments, templates, and messaging. Always search tools first for current schemas.

news-api-automation

23
from christophacham/agent-skills-library

Automate News API tasks via Rube MCP (Composio). Always search tools first for current schemas.

nango-automation

23
from christophacham/agent-skills-library

Automate Nango tasks via Rube MCP (Composio). Always search tools first for current schemas.

logo-dev-automation

23
from christophacham/agent-skills-library

Automate Logo Dev tasks via Rube MCP (Composio). Always search tools first for current schemas.

hashnode-automation

23
from christophacham/agent-skills-library

Automate Hashnode tasks via Rube MCP (Composio). Always search tools first for current schemas.

genderapi-io-automation

23
from christophacham/agent-skills-library

Automate Genderapi IO tasks via Rube MCP (Composio). Always search tools first for current schemas.

gender-api-automation

23
from christophacham/agent-skills-library

Automate Gender API tasks via Rube MCP (Composio). Always search tools first for current schemas.