Launch Darkly Automation

---
name: LaunchDarkly Automation
description: "Automate LaunchDarkly feature flag management -- list projects and environments, create and delete trigger workflows, and track code references via the Composio MCP integration."
requires:
  mcp:
    - rube
executor: HYBRID
skill_id: integrations.composio.launch-darkly-automation
status: ADOPTED
security: {level: standard, pii: false, approval_required: false}
extends: integrations.composio.meta
toolkit: launch-darkly-automation
# Phase3: This stub routes to the meta-skill. See skills/integrations/composio/SKILL.md for full protocol.
anchors:
  - automation
  - integration
  - api
  - workflow
tier: 3
input_schema:
  - name: code_or_task
    type: string
    description: "Code snippet, script, or task description to process"
    required: true
  - name: context
    type: string
    description: "Additional context or background information"
    required: false
output_schema:
  - name: result
    type: string
    description: "Generated or refactored code output"
  - name: explanation
    type: string
    description: "Explanation of changes or implementation decisions"
what_if_fails: >
  FALLBACK: If Launchdarkly cannot complete, provide partial results with
  explicit gaps noted. Never block workflow silently.
  ESCALATE: If core capability is unavailable, suggest nearest alternative skill.
  RULE: Always explain what failed and what manual steps can substitute.
---

# 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)*

## Why This Skill Exists
Stub for the `launch-darkly-automation` toolkit in the Composio integration ecosystem.
Extends `integrations.composio.meta` — see the meta-skill for full protocol.

## When to Use
Use when automating `launch-darkly-automation` tasks via Rube MCP (Composio).
For generic Composio queries, use `integrations.composio.meta` directly.

## What If Fails
See `skills/integrations/composio/SKILL.md` (meta-skill) for full fallback protocol.
RULE: Never block workflow — always suggest manual alternative if automation fails.