README

This skill teaches agents how to:

• Diagnose “why didn’t Release Autopilot classify my PR?” (mapped repo → effective repo setting → account settings, on accounts that still use them) before changing anything
• Read account-wide Release Autopilot defaults
• Confirm every write (account, map, repo override, unmap) before calling MCP
• List GitHub App install repos as owner/name

Installation (Local)

• Generic: copy skills/release-autopilot/launchdarkly-release-autopilot-settings/ into your client’s skills path

Prerequisites

The remotely hosted LaunchDarkly MCP server must expose the Release Autopilot settings tools (get-automations, update-automations, and delete-automations-repo-settings). If get-automations returns githubConnectUrl, give the user that link. This skill does not complete GitHub OAuth itself.

The endpoints behind these tools require the Release Autopilot add-on, so accounts without it enabled get 404s.

Usage

Related

• LaunchDarkly Release Autopilot Onboarding: step-by-step first-time setup
• LaunchDarkly Flag Create: Create flags after Release Autopilot is mapped
• LaunchDarkly MCP Server (opens in a new tab)
• LaunchDarkly Docs (opens in a new tab)

License

Apache-2.0