Index of every page on this site: llms.txt
All skills
launchdarkly avatar

/launchdarkly-release-plans

@f0ee110 official
Run it yourself

List, create, edit, make default, and delete LaunchDarkly release plans of both kinds: environment release plans (one environment's phases, rollout steps, and rollback metrics, with starter plans) and flag release plans (a project's environments in release order, each with its environment release plan, which Release Autopilot proposes releases from on pull requests). Also starts a flag's release from a flag release plan. Use when the user wants to see, list, build, change, or remove a release plan (such as 'show me the flag release plans' or 'what release plans does production have'), set an environment's or a project's default plan, or when another skill such as Release Autopilot onboarding needs release plans planned or created. For first-time Release Autopilot setup, use launchdarkly-release-autopilot-onboarding, which follows this skill.

Use this Skill: https://skilld.dev/gh/launchdarkly/ai-tooling/launchdarkly-release-plans

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

README.md

≈664 tokens on demand. Your agent reads this file only when SKILL.md points to it.

LaunchDarkly Release Plans Skill

An Agent Skill for both kinds of LaunchDarkly release plan:

  • Environment release plans: how a flag releases in one environment (phases, rollout steps, holds, and rollback metrics). Each environment has a default plan.
  • Flag release plans: a project's environments in release order, each with its environment release plan. Release Autopilot proposes releases on pull requests from these plans. The flag-release skill also starts a flag's release from them, and from each environment's release plan when the project has none.

Overview

This skill teaches agents how to:

  • List and show both kinds of plan, and each environment's and project's default
  • Create environment release plans from starter plans (progressive, or guarded with rollback metrics) or step by step, after checking the randomization unit and metrics
  • Build or update the project's flag release plan from existing environment release plans, and prompt for a release plan first when an environment has none
  • Edit, make default, and delete both kinds of plan, confirming every write first
  • Start a flag's release from a flag release plan
  • Plan without writing ("record only"), for skills such as Release Autopilot onboarding that confirm and write later

Installation (Local)

  • Generic: copy skills/release-autopilot/launchdarkly-release-plans/ into your client's skills path

Prerequisites

  • The hosted LaunchDarkly MCP server, for both kinds of plan. Its flag release plan tools are still reaching accounts.
  • When the server has no tool for an operation (flag release plans without their tools, deleting an environment release plan): the agent shows the REST command, and you run it in your own terminal with your LaunchDarkly API access token in LD_ACCESS_TOKEN, then paste the output back. The agent never runs these commands. Never paste a token into the chat.

These REST endpoints are in beta, and every command sends LD-API-Version: beta. ldcli has no command for these endpoints, so the commands use curl.

Usage

Which release plans does production in project default have?
Create a release plan for production in project default and make it the default
Build the flag release plan for project default: test, then production, as the default

Related

License

Apache-2.0

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert1d3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    This skill provides a secure interface for managing LaunchDarkly release plans. It implements industry-standard safety practices, such as ensuring sensitive API tokens are never handled by the AI and requiring explicit user confirmation before any modifications are made to production settings. For advanced operations, it provides clear instructions for users to run commands locally, maintaining a secure boundary between the AI and the user's credentials.

  • Socket2d

    No alerts

  • Snyk1d

    Risk: CRITICAL · 1 issue

Signed by skilld at f0ee110. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 days ago
metadata
{
  "author": "launchdarkly",
  "version": "1.2.1"
}
Other metadata
compatibility
Uses the hosted LaunchDarkly MCP server. When the server has no tool for an operation (flag release plans before their tools reach the account, deleting an environment release plan), the user runs the REST API (beta) command that the skill shows in their own terminal.

README badge

README badge for launchdarkly/ai-tooling/launchdarkly-release-plans