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

/launchdarkly-automations-archival-settings

@f0ee110 official
Run it yourself

Read and change a LaunchDarkly project's Automations auto-archival settings via the hosted MCP. Auto-archival archives flags that are ready to archive after a grace period, or creates approval requests for them. Use when the user wants to see or change the grace period, approval requirement, run limit, recheck cadence, or notification recipients, turn automatic archival off or on, or asks why a flag was or was not archived automatically. 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-archival-settings

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

README.md

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

LaunchDarkly Automations Auto-archival Settings Skill

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

Overview

This skill teaches agents how to:

  • Read a project's grace period, approval requirement, run limit, and notification recipients
  • Change those settings or turn automatic archival off, confirming every write first
  • Hand turning archival on to a person, who confirms its risk on the Automations page
  • Explain why a flag was or was not archived automatically

Installation (Local)

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

Prerequisites

The remotely hosted LaunchDarkly MCP server must expose get-automations with section: "archival" and update-automations with archival. Without them, the skill guides the browser steps instead. Accounts without automatic archival get an error saying it is not available yet.

Usage

How long does automatic archival wait before archiving a flag in project default?
Require approval before automatic archival archives flags in project default
Why wasn't old-checkout archived automatically?

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 safe. It defines a set of operations for managing LaunchDarkly auto-archival settings via an official Model Context Protocol (MCP) server. It includes robust internal safety guidelines, such as mandatory user confirmation for all modifications and a requirement for manual human intervention to enable archival features, which prevents the agent from making uncontrolled high-risk changes.

  • 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-archival-settings