skilld
All skills
launchdarkly avatar

/launchdarkly-flag-discovery

@be58859 official
by launchdarklylaunchdarkly/agent-skills25 stars
10

Audit your LaunchDarkly feature flags to understand the landscape, find stale or launched flags, and assess removal readiness. Use when the user asks about flag debt, stale flags, cleanup candidates, flag health, or wants to understand their flag inventory.

Ask your Agent

Use this Skill: https://skilld.dev/gh/launchdarkly/agent-skills/launchdarkly-flag-discovery

This session only. Nothing lands on disk.

README.md

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

LaunchDarkly Flag Discovery Skill

An Agent Skill for auditing and understanding your LaunchDarkly feature flag landscape.

Overview

This skill teaches agents how to:

  • Survey the full feature flag inventory in a project
  • Identify stale, inactive, or fully-launched flags
  • Assess whether specific flags are ready for removal
  • Provide prioritized, actionable recommendations

Installation (Local)

For now, install by placing this skill directory where your agent client loads skills.

Examples:

  • Generic: copy skills/feature-flags/launchdarkly-flag-discovery/ into your client's skills path

Prerequisites

This skill requires the remotely hosted LaunchDarkly MCP server to be configured in your environment. The remote server provides higher-level, agent-optimized tools that orchestrate multiple API calls and return pruned, actionable responses.

Refer to your LaunchDarkly account settings for instructions on connecting to the remotely hosted MCP server.

Usage

Once installed, the skill activates automatically when you ask about flag health or inventory:

What's the state of our feature flags?
Which flags are stale and should be cleaned up?
Is the `dark-mode` flag ready to be removed?

Structure

launchdarkly-flag-discovery/
├── SKILL.md
├── marketplace.json
├── README.md
└── references/
    ├── flag-health-signals.md
    └── removal-readiness-checklist.md

Related

License

Apache-2.0

Source: SKILL.md on GitHub

Third-party checks

1 warning16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill provides workflow guidance and documentation for auditing LaunchDarkly feature flags via an MCP server. It contains no executable code or malicious patterns.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    5/5 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at be58859. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 6 months ago

Capability

compatibility
Requires the remotely hosted LaunchDarkly MCP server
metadata
{
  "author": "launchdarkly",
  "version": "1.0.0-experimental"
}

Topics

  • MCP
  • launchdarkly
  • feature-flags
  • flag-audit
  • flag-cleanup
  • flag-health
  • inventory

README badge

README badge for launchdarkly/agent-skills/launchdarkly-flag-discovery

What it does

Audits LaunchDarkly feature flags to identify stale, launched, or inactive flags and assess removal readiness. Uses the LaunchDarkly MCP server to explore flag inventory, categorize cleanup candidates, and provide removal safety verdicts based on lifecycle state, staleness, and cross-environment consistency.

Generated from the current SKILL.md.

Frequently asked

Does this skill remove flags from code or just identify candidates?
This skill only audits and identifies cleanup candidates. For actual code removal, use the launchdarkly-flag-cleanup skill.
What MCP server does this require?
The remotely hosted LaunchDarkly MCP server. Without it, the skill cannot access flag data.
Can I audit flags across multiple environments at once?
Yes. The skill can list flags in a specific environment and use get-flag-status-across-envs to check consistency across all environments.
What counts as a stale flag?
Flags with no SDK evaluations in the specified period (default 30 days), plus flags created but never evaluated and fully rolled-out flags with no recent changes. The find-stale-flags tool categorizes these separately.
How do I know if a flag is safe to remove?
Use check-removal-readiness for a specific flag. It returns a verdict (safe, caution, or blocked) based on dependencies, code references, and targeting rules.

Generated from the current SKILL.md. These answers refresh after source changes.