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.

referencesauto-cleanup.md

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

Auto-cleanup

Auto-cleanup runs the Release Autopilot agents on a schedule to find flags that are ready for code removal and open pull requests that remove their code. It is set per project. Onboarding sets it through the MCP with update-automations (projectKey plus a cleanup object); launchdarkly-automations-cleanup-settings changes it later.

Read the current settings first with get-automations (section: "cleanup", projectKey). settings.schedule of disabled means it is off; upcoming.flagKeys and nextRunAt preview the next run.

The onboarding write sends only:

  • schedule: weekly (recommended), daily, or monthly
  • repositories: the owner/name repos cleanup opens pull requests in, all on the GitHub App install
  • maxJobsPerRun: pull requests per run (3 is a safe start)

Leave flagStates at its default (readyToArchive). Lists replace the whole stored list: when adding repositories to a running cleanup, send the existing repositories from the read plus the new ones. Saving makes the calling member the one whose permissions cleanup jobs use; if that member loses access, someone else must save the settings again. Any schedule other than disabled makes LaunchDarkly open pull requests, so the Step 7 line must state the schedule, repositories, and pull requests per run.

In the UI, the same settings are in the Automated flag cleanup section of /projects/{projectKey}/settings/automations.

Docs: Automated flag cleanup

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