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-archival.md

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

Auto-archival

Auto-archival archives flags that are ready to archive, after archival safety checks and a grace period. It is set per project, in the Automatic archival section of the project's Settings > Automations page. Turning it on needs a person to confirm its risk in the browser, so onboarding always makes it a browser step. On an MCP server with get-automations-archival and update-automations-archival, the launchdarkly-automations-archival-settings skill can read and change its other settings later.

For each project, give the user /projects/{projectKey}/settings/automations on their LaunchDarkly instance (for example https://app.launchdarkly.com, or their EU or federal URL). If the link opens the general project settings page instead, the account uses the older settings pages, and they use /projects/{projectKey}/settings/lifecycle. In the "Automatic archival" section they:

  1. Turn on Enable automatic archival, and confirm in the "Enable automatic archival?" dialog.
  2. Set the grace period before a ready flag is archived.
  3. If the section shows Require approval before archiving, choose whether archivals need approval.
  4. Click Save.

"View ready to archive flags" and "View auto-archived flags" open the flags list filtered to each set, so they can check what it will do and what it did.

If the page has no "Automatic archival" section, the account does not include the feature: record it as a follow-up, not as done.

Record the result as reported by the user. Onboarding does not verify it.

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