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.

referencesbrowser-steps.md

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

Auto-archival in the browser

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

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, and they use /projects/{projectKey}/settings/lifecycle. In the "Automatic archival" section they:

  1. Turn on Enable automatic archival, and confirm in the "Enable automatic archival?" dialog.
  2. Set the grace period before a ready flag is archived.
  3. If the section shows Require approval before archiving, choose whether archivals need approval.
  4. Click Save.

"View ready to archive flags" and "View auto-archived flags" open the flags list filtered to each set.

If the page has no "Automatic archival" section, the feature is not available for their account yet. 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 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