Agent skill · software engineering · composiohq
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.
Why this skill is useful
Adds specific commands and workflows for managing LaunchDarkly feature flags that the AI wouldn't reliably generate on its own.
What it needs
Requires launchdarkly account access. About 2k tokens when loaded. Last updated 2026-07-24. 71,973 stars on the source repository.
What this skill does
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/launchdarkly --- 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 LAUNCHDARKLYLISTPROJECTS to discover all projects and their keys for subsequent operations. 2. Get Environments for a Project Use LAUNCHDARKLYGETENVIRONMENTS to list all environments within a project (production, staging, test, etc.). 3. Create a Flag Trigger Workflow Use LAUNCHDARKLYCREATETRIGGERWORKFLOW to set up automated flag toggles triggered by external events (webhooks, Datadog alerts, etc.). The trigger generates a unique webhook URL that can be called to execute the configured flag action. 4. Delete a Flag Trigger Workflow Use LAUNCHDARKLYDELETETRIGGERWORKFLOW to permanently remove a trigger and its URL. Warning: Deletion is irreversible. The trigger and its URL cannot be recovered. 5. List Code Reference Repositories Use LAUNCHDARKLYLISTCODEREFERENCEREPOSITORIES to track where feature flags are used in your codebase. Note: Code references is an Enterprise feature requiring code-reference-repository write permissions. --- Known Pitfalls Pitfall Detail --------- -------- Project key discovery Always use LAUNCHDARKLYLISTPROJECTS 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 LAUNCHDARKLYDELETETRIGGERWORKFLOW, the trigger URL is unrecoverable. Enterprise-only code refs LAUNCHDARKLYLISTCODEREFERENCEREPOSITORIES requires Enterprise plan and write permissions. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills composiohq/launch-darkly-automation