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.

referencesgithub-troubleshooting.md

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

GitHub still not connected after "Done"

The connect link acts on whatever LaunchDarkly session the browser has. This connection is signed in as the member from Step 1 (get-member-self). If the browser is signed in to a different LaunchDarkly account, or as a different member, the user installs or authorizes the App there, and this connection still sees nothing.

Check the causes in this order. Stop at the first that applies.

  1. Different LaunchDarkly account or member in the browser. SKILL.md Step 3 asks about this first. An install made from the other account stays there; that account's admin can remove it if it was a mistake.
  2. Different LaunchDarkly instance. The browser is on another instance (for example EU or federal) than this connection. Give the link with the instance this connection uses.
  3. Authorized with the wrong GitHub account (flow=authorize remains). The GitHub account they authorized cannot see the organization's install. They reconnect with a GitHub account that is a member of that organization.
  4. Installed on a different GitHub organization. The App is now installed, but not on the organization that owns their repo. See the repo-owner check in Step 4.

If none applies, say what you checked and stop. Do not retry the link more than once without a change.

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