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.

referencesbrowser-steps.md

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

Auto-cleanup in the browser

Use these steps only when the MCP server's get-automations has no section argument for cleanup.

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 does not have the Automations page yet: they use /projects/{projectKey}/settings/lifecycle, or /projects/{projectKey}/settings/vega if that page has no "Automated flag cleanup" section. In the "Automated flag cleanup" section they:

  1. Check Enable automated flag cleanups.
  2. Choose a Schedule frequency.
  3. Set Max cleanup jobs per run.
  4. Select the GitHub repositories to clean up. At least one is required.
  5. Optionally add Additional context for the cleanup agent.
  6. Click Save.

Record the result as reported by the user. Without the tools, it cannot be verified.

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