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

/launchdarkly-release-autopilot-settings

@f0ee110 official
Run it yourself

Configure LaunchDarkly Release Autopilot settings (GitHub App auto-flagging and auto-releasing) via the hosted MCP, or diagnose why a pull request was not classified / auto-flagged. Use when the user wants to turn on auto-flagging, map a GitHub repo to a LaunchDarkly project, change Release Autopilot account defaults, unmap a repo, or asks why Release Autopilot did not classify their PR. For first-time setup (pick capabilities, connect GitHub, choose inference, set up environment release plans and the project's flag release plan), use launchdarkly-release-autopilot-onboarding instead. For release plans, use launchdarkly-release-plans. For auto-cleanup or auto-archival settings, use launchdarkly-automations-cleanup-settings or launchdarkly-automations-archival-settings.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

README.md

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

LaunchDarkly Release Autopilot Settings Skill

An Agent Skill for configuring Release Autopilot (GitHub App auto-flagging and auto-releasing) through the LaunchDarkly MCP, and for diagnosing why a PR was not classified.

Overview

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

Why didn't Release Autopilot classify my pull request?
Turn on auto-flagging and map launchdarkly/gonfalon to project default
Which GitHub repos are mapped for Release Autopilot, and which can I map?

Related

License

Apache-2.0

Source: SKILL.md on GitHub

No rule matched.

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.

1 warning4d3 checks · Risk SAFE
  • Gen Agent Trust Hub4d

    This skill provides instructions for an AI agent to manage LaunchDarkly Release Autopilot settings via a dedicated Model Context Protocol (MCP) server. It implements robust security patterns, including a mandatory human-in-the-loop confirmation for all state-changing operations and a 'fail-closed' diagnostic approach. All external resources, including the required MCP server and documentation links, originate from trusted or well-known vendor infrastructure (LaunchDarkly and Atlassian).

  • Socket6d

    No alerts

  • Snyk4d

    Risk: MEDIUM · 1 issue

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 last week
compatibility
Requires the remotely hosted LaunchDarkly MCP server
metadata
{
  "author": "launchdarkly",
  "version": "1.6.1-experimental"
}

README badge

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