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

/launchdarkly-release-autopilot-onboarding

@f0ee110 official
Run it yourself

Step-by-step onboarding wizard for LaunchDarkly Release Autopilot: pick capabilities (auto-flagging, auto-releasing, auto-cleanup, auto-archival), connect the GitHub App, map repositories to projects, choose which AI model account runs the agents (LaunchDarkly's by default, or your own Anthropic or OpenAI key), set up environment release plans (with starter plans) and the project's flag release plan, and turn on scheduled flag cleanup and archival. Use when the user wants to set up, onboard to, preview, or continue setting up Release Autopilot. For a single settings change or 'why didn't my PR get classified?', use launchdarkly-release-autopilot-settings instead.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

README.md

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

LaunchDarkly Release Autopilot Onboarding Skill

An Agent Skill that walks a user through setting up Release Autopilot: pick capabilities, connect the GitHub App, map repositories, choose which AI model account runs the agents, set up environment release plans (with starter plans) and the project's flag release plan, set auto-cleanup, and guide turning on auto-archival.

Overview

This skill teaches agents how to:

  • Ask which capabilities the user wants (auto-flagging, auto-releasing) and set up only what those need
  • Hand the user the GitHub App install or authorize link, and continue after they finish
  • Map chosen owner/name repos to LaunchDarkly projects
  • Set auto-cleanup through the MCP, and guide turning on auto-archival on the project's Automations page
  • Explain whose AI model account runs the agents (LaunchDarkly's by default, or the user's own Anthropic or OpenAI key) and guide bring-your-own-key setup
  • Set up environment release plans (with starter plans) and the project's flag release plan for auto-releasing, with the launchdarkly-release-plans skill, or give the flag release plan commands as a follow-up
  • Confirm GitHub works, list exactly which repos were set up, and offer a test pull request and next steps
  • Confirm one plan that lists every write before making any change, then verify

Installation

Install the LaunchDarkly plugin first. It includes this skill and the LaunchDarkly MCP server that the skill needs.

  • Claude Code: run /plugin marketplace add launchdarkly/ai-tooling, then /plugin install launchdarkly@launchdarkly-ai-tooling. Then open /mcp and sign in to the launchdarkly server.
  • Cursor: open Settings > Plugins, search for LaunchDarkly, and install it.

The skill is in Claude Code plugin 1.0.3 and Cursor plugin 1.0.4 and later. With an earlier plugin, a request to set up Release Autopilot starts the SDK onboarding skill instead, so update the plugin first.

  • Other clients: copy skills/release-autopilot/launchdarkly-release-autopilot-onboarding/ into your client's skills path, and connect the hosted LaunchDarkly MCP server.

Prerequisites

The remotely hosted LaunchDarkly MCP server must expose the Release Autopilot tools (get-automations, update-automations), and get-environment-release-plans, create-environment-release-plan, update-default-environment-release-plan, and get-metrics for auto-releasing. The flag release plan uses get-flag-release-plans, create-flag-release-plan, and update-flag-release-plan when the server has them. These tools are still reaching accounts. Without them, the agent shows the flag release plan's REST commands, you run them in your own terminal with your LaunchDarkly API access token, and you paste the output back. Never paste a token into the chat. Accounts without the Release Autopilot add-on enabled get 404s.

Usage

Set up Release Autopilot for this repo
Onboard us to Release Autopilot with auto-flagging and auto-releasing

Related

License

Apache-2.0

Source: SKILL.md on GitHub

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.

No alerts1d3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    This skill provides a guided onboarding wizard for LaunchDarkly Release Autopilot. It follows robust security practices, including a mandatory human-in-the-loop confirmation step for all modifications, explicit warnings against sharing API tokens in chat, and directing users to perform sensitive credential setup within their own browser. The skill interacts with the LaunchDarkly platform via a standard MCP server, ensuring a clear boundary between the AI's instructions and system execution.

  • Socket2d

    No alerts

  • Snyk1d

    Risk: LOW · No issues

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 4 days ago
compatibility
Requires the remotely hosted LaunchDarkly MCP server
metadata
{
  "author": "launchdarkly",
  "version": "1.2.3"
}

README badge

README badge for launchdarkly/ai-tooling/launchdarkly-release-autopilot-onboarding