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.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 1
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 76732a50098be98a… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
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
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
Files
1- SKILL.md
8e3a6cd8f54.8 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from ComposioHQ/awesome-claude-skills8
Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
Automate SEO research with Ahrefs -- analyze backlink profiles, research keywords, track domain metrics history, audit organic rankings, and perform batch URL analysis through the Composio Ahrefs integration.
Automate web scraping and data extraction with Apify -- run Actors, manage datasets, create reusable tasks, and retrieve crawl results through the Composio Apify integration.
Automate Apollo.io lead generation -- search organizations, discover contacts, enrich prospect data, manage contact stages, and build targeted outreach lists -- using natural language through the Composio MCP integration.
Automate recruiting and hiring workflows in Ashby -- manage candidates, jobs, applications, interviews, and notes through natural language commands.
Automate Attio CRM operations -- search records, query contacts and companies with advanced filters, manage notes, list attributes, and navigate your relationship data -- using natural language through the Composio MCP integration.
Braintree Automation: manage payment processing via Stripe-compatible tools for customers, subscriptions, payment methods, and transactions
Related integrations skillsscan passed
Qdrant provides client SDKs for various programming languages, allowing easy integration with Qdrant deployments.
Measures whether an automation suite builds release confidence via feedback-loop length, suite reliability, release cadence, and production escape rate, and emits a release_confidence verdict. Use when judging suite value, ROI, or pre-release trust; not for writing or healing tests.
Qdrant provides client SDKs for various programming languages, allowing easy integration with Qdrant deployments.
Handles annotated matrices in single-cell analysis, .h5ad and Zarr files, and integration with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Browser automation + AI test authoring via kane-cli - run browser objectives, generate & refine test scenarios/cases from a description, design requirement-linked test suites from a PRD/spec (assurance), parse NDJSON output, inspect logs, save runnable _test.md. Use for any task requiring a real bro