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

/launchdarkly-flag-command

@f0ee110 official
Run it yourself

Resolve `/flag` style requests into the right LaunchDarkly flag lookup flow. Use when the user types `/flag`, asks to quickly find a flag by name/key, wants a direct flag detail summary, or needs fast disambiguation between similar flags.

Use this Skill: https://skilld.dev/gh/launchdarkly/ai-tooling/launchdarkly-flag-command

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈66 tokens for metadata: the name and description. ≈1.3k when used: this file. ≈581 more on demand in 2 files.

Description uses 3.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈266 characters, or 3.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

LaunchDarkly Flag Command Router

You're using a skill that standardizes quick /flag requests. Your job is to parse the user intent, resolve the requested flag with minimal friction, return an actionable summary, and route to deeper workflows when needed.

Scope Boundary

This skill is a read-only lookup entrypoint. It returns flag details and routes forward.

Hard constraints — you MUST NOT:

  • Create, toggle, update, or delete flags
  • Assess whether a flag is safe to remove, stale, or ready for cleanup
  • Provide a "verdict", "safe to remove" conclusion, removal steps, or "before removing" advice
  • Offer to archive or delete the flag

When the user asks about removal or staleness, your entire response for that part must be the flag summary table followed by this exact routing message (you may rephrase slightly but must keep the substance):

This quick lookup can only show you the flag's current config. To assess whether it's safe to remove, you need the flag discovery or flag cleanup skill — they scan code references, check status across all environments, and analyze downstream dependencies.

That's it. No analysis. No bullet points. No verdict. The removal question is answered by the routing message, not by you.

Prerequisites

This skill requires the remotely hosted LaunchDarkly MCP server to be configured in your environment.

Required MCP tools:

  • get-flags — without flagKey, search and disambiguate flag candidates; with flagKey, fetch detailed configuration for the resolved flag

Optional MCP tools:

  • get-flag-status-across-envs — compare lifecycle status across environments
  • get-flag-health — quick health snapshot for a single flag

Command Contract

Treat these forms as equivalent intents:

  • /flag <query>
  • flag <query>
  • "find flag <query>"
  • "show me <query> flag"

Use production as the default environment unless the user specifies another environment.

Workflow

Step 1: Parse and Normalize Input

  1. Extract the query text after /flag.
  2. If no query is provided, ask for one concise identifier (flag key, name fragment, or tag).
  3. Capture optional hints from the request:
    • Environment (staging, production, etc.)
    • Project key
    • Preference for exact key vs fuzzy search

Step 2: Resolve the Flag

Use get-flags first unless the user clearly provided an exact key and project.

  1. Search with get-flags using the query.
  2. If one clear exact match exists, resolve to that flag.
  3. If multiple plausible matches exist, return a short disambiguation list (key + name + state) and ask the user to pick.
  4. If no matches exist, tell the user and suggest one broader query.

Step 3: Return a Useful Summary

For a resolved flag, call get-flags and return:

  1. Flag key and name
  2. Environment state (on/off)
  3. Off variation and fallthrough behavior
  4. Rule/target complexity (simple vs complex)
  5. Direct LaunchDarkly URL for the flag (when project + key are known)

If the user asked about removal, staleness, or cleanup (e.g., "is this safe to remove?", "can I clean this up?", "is this stale?"):

Show ONLY the summary table above, then write:

This quick lookup can only show you the flag's current config. To assess whether it's safe to remove, you need the flag discovery or flag cleanup skill — they scan code references, check status across all environments, and analyze downstream dependencies.

Do not add a verdict, bullet-point analysis, removal steps, "before removing" checklist, or an offer to archive/delete. The removal question is fully answered by the routing message above. Proceed to Step 4.

Step 4: Route to the Right Follow-up Workflow

After returning the summary, check whether the user's request implies a deeper workflow. If it does, name the skill and stop — do not attempt the workflow yourself.

User intent Route to
Create or modify a flag flag create skill
Change targeting or rollout flag targeting skill
"Is this safe to remove?", "Is this stale?", cleanup flag discovery / flag cleanup

For removal/staleness questions specifically: follow the Scope Boundary instructions above — summary table only, then route. No verdict.

Output Style

Keep /flag responses brief and operational:

  • Start with the resolved flag (or disambiguation list)
  • Include only the minimum config details needed for the next action
  • End with one clear next step question when user intent is ambiguous

Important Context

  • /flag is a fast entrypoint, not a full lifecycle workflow.
  • Prefer disambiguation over guessing when multiple flags match.
  • Treat project + environment as first-class context; avoid hidden assumptions.
  • When sharing rollout percentages, always use human-readable percentages.
  • Never improvise removal, staleness, or cleanup analysis. Always route to the dedicated skill.

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 alerts15d3 checks · Risk SAFE
  • Gen Agent Trust Hub15d

    The skill facilitates quick feature flag lookups via the LaunchDarkly API. It is designed as a read-only entry point with explicit constraints against performing modifications. The processing of external flag metadata introduces a standard surface for indirect prompt injection.

  • Socket15d

    No alerts

  • Snyk15d

    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": "1.0.0-experimental"
}
  • MCP
  • launchdarkly
  • flags
  • feature-flags
  • lookup
  • routing

README badge

README badge for launchdarkly/ai-tooling/launchdarkly-flag-command

Resolves `/flag` queries into LaunchDarkly flag lookups, returning flag details (key, name, environment state, targeting rules) and routing to specialized skills for creation, targeting changes, or cleanup assessment. Use this as the read-only entrypoint when a user asks to quickly find or inspect a flag by name or key.

Generated from the current SKILL.md.

Does this skill create or modify flags?
No. This is a read-only lookup entrypoint. It resolves flag details and routes to other skills for creation, targeting changes, or removal decisions.
What MCP server does this require?
The remotely hosted LaunchDarkly MCP server, configured in your environment. It uses list-flags and get-flag tools as core dependencies.
Can this skill assess whether a flag is safe to remove?
No. For removal or staleness questions, it returns the flag summary and routes to the flag discovery or flag cleanup skill instead.
What environment does this use by default?
Production, unless the user specifies a different environment like staging.
Does this handle flag disambiguation?
Yes. If multiple flags match the query, it returns a short list with key, name, and state, then asks the user to pick one.

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