launchdarkly

name	launchdarkly
description	Inspect LaunchDarkly feature flags, environments, segments, and metrics through the read-only ldcli wrapper.

When to use

Use this skill when:

• The user asks whether a feature flag is enabled in a given environment
• Investigating rollout state, segments, or related metrics during debugging
• Cross-referencing application behavior with LaunchDarkly configuration
• You need the current LaunchDarkly source of truth instead of guessing from code

---

Overview

This skill provides read-only access to LaunchDarkly via CLI:

ldcli <resource> <action> [options]

Supported resources:

• flags
• environments
• projects
• segments
• metrics

Use resource help for command discovery:

ldcli flags --help
ldcli segments --help

---

Auth and output

• Don't pass --access-token; auth is injected for you
• --output json is auto-appended unless you already pass an explicit output flag
• Responses are machine-readable JSON; inspect fields directly instead of relying on plaintext formatting

---

Core workflows

1. List flags in a project

ldcli flags list --project default --limit 50

---

2. Get a flag's full state

ldcli flags get my-flag --project default --environment production

Use this to inspect per-environment targeting and rollout state.

---

3. List environments in a project

ldcli environments list --project default

---

4. List segments for an environment

ldcli segments list --project default --environment production

---

5. List metrics in a project

ldcli metrics list --project default

---

Execution strategy

1. Start with the narrowest resource and project possible.
2. Add --environment for flag or segment work when the question is environment-specific.
3. Prefer get only when you already know the exact flag key; otherwise start with list.
4. Summarize the relevant JSON fields instead of dumping large payloads.

---

Constraints

• Surface is read-only inspection of the resources listed above; mutating verbs and unlisted resources return a policy denial
• Scoped API calls for flags, environments, segments, and metrics require --project <key>
• metrics supports list only

---

Gotchas

• ldcli flags get exposes environment-specific state under environments[<env-key>]
• ldcli flags --help is allowed for discovery, but real resource queries still need explicit scope
• If the user needs to change LaunchDarkly state, tell them the current integration is read-only