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

/launchdarkly-automations-cleanup-settings

@f0ee110 official
Run it yourself

Read and change a LaunchDarkly project's Automations auto-cleanup settings via the hosted MCP. Auto-cleanup runs on a schedule and opens pull requests that remove the code for flags that are ready. Use when the user wants to turn automated flag cleanup on or off, change its schedule, repositories, flag states, job limit, or agent instructions, see which flags the next run will pick up, or asks why cleanup did not open a pull request. For first-time setup of every Release Autopilot capability, use launchdarkly-release-autopilot-onboarding.

Use this Skill: https://skilld.dev/gh/launchdarkly/ai-tooling/launchdarkly-automations-cleanup-settings

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

README.md

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

LaunchDarkly Automations Auto-cleanup Settings Skill

An Agent Skill for reading and changing a project's auto-cleanup settings (the "Automated flag cleanup" section of the project's Automations page) through the LaunchDarkly MCP.

Overview

This skill teaches agents how to:

  • Read a project's cleanup schedule, repositories, limits, and the flags the next run will pick up
  • Turn automated flag cleanup on, change it, or turn it off, confirming every write first
  • Explain why cleanup did not open a pull request for a flag

Installation (Local)

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

Prerequisites

The remotely hosted LaunchDarkly MCP server must expose get-automations with section: "cleanup" and update-automations with cleanup. Without them, the skill guides the browser steps instead.

Usage

Turn on automated flag cleanup for project default, weekly, in acme/web
Which flags will the next cleanup run pick up in project default?
Why didn't flag cleanup open a pull request for old-checkout?

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.

No alerts14d3 checks · Risk SAFE
  • Gen Agent Trust Hub14d

    The skill is generally safe and incorporates strong security practices like mandatory user confirmation for changes and least-privilege repository access. However, it presents an indirect prompt injection surface as it processes and stores custom agent instructions (customContext) that are interpreted by a downstream automation agent, though the risk is mitigated by the skill's transparent confirmation workflows.

  • Socket14d

    No alerts

  • Snyk14d

    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 2 weeks ago
compatibility
Requires the remotely hosted LaunchDarkly MCP server
metadata
{
  "author": "launchdarkly",
  "version": "0.1.0-experimental"
}

README badge

README badge for launchdarkly/ai-tooling/launchdarkly-automations-cleanup-settings