launchdarkly-flag-command

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

LaunchDarkly Flag Command Router

LaunchDarkly 标志命令路由器

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.

你正在使用一款标准化快速

/flag

请求的Skill。你的任务是解析用户意图，以最小的阻力解析请求的标志，返回可执行的摘要，并在需要时路由到更深层的工作流。

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.

该Skill是一个只读查询入口。它返回标志详情并进行路由。

严格约束——禁止以下操作：

创建、切换、更新或删除标志
评估标志是否可以安全移除、是否已过时或是否可清理
提供“结论”、“可安全移除”的判断、移除步骤或“移除前”建议
提供归档或删除标志的服务

当用户询问移除或过时相关问题时，针对该部分的完整回复必须先显示标志摘要表，然后附上以下确切的路由信息（可稍作措辞调整，但必须保留核心内容）：

此快速查询仅能显示标志的当前配置。若要评估是否可安全移除，你需要使用flag discovery或flag cleanup Skill——它们会扫描代码引用、检查所有环境中的状态并分析下游依赖。

仅此而已。禁止分析、禁止使用项目符号、禁止给出结论。移除相关问题仅由上述路由信息回答，你无需额外回应。

Prerequisites

前提条件

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

Required MCP tools:

```
list-flags
```
— search and disambiguate flag candidates
```
get-flag
```
— fetch detailed configuration for a 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

使用该Skill需要在你的环境中配置远程托管的LaunchDarkly MCP服务器。

必需的MCP工具：

```
list-flags
```
— 搜索并区分候选标志
```
get-flag
```
— 获取已解析标志的详细配置

可选的MCP工具：

```
get-flag-status-across-envs
```
— 对比不同环境中的生命周期状态
```
get-flag-health
```
— 单个标志的快速健康快照

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.

将以下形式视为等效意图：

```
/flag <查询内容>
```
```
flag <查询内容>
```
"查找标志 <查询内容>"
"展示 <查询内容> 标志"

除非用户指定其他环境，否则默认使用

production

环境。

Workflow

工作流

Step 1: Parse and Normalize Input

步骤1：解析并标准化输入

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

提取
```
/flag
```
后的查询文本。
如果未提供查询内容，请用户提供一个简洁的标识符（标志键、名称片段或标签）。
从请求中捕获可选提示：
- 环境（
```
staging
```
  、
```
production
```
  等）
- 项目键
- 精确键匹配或模糊搜索的偏好

Step 2: Resolve the Flag

步骤2：解析标志

Use

list-flags

first unless the user clearly provided an exact key and project.

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

除非用户明确提供了精确的键和项目，否则优先使用

list-flags

。

使用查询内容通过
```
list-flags
```
进行搜索。
如果存在一个明确的精确匹配项，则解析为该标志。
如果存在多个合理匹配项，则返回一个简短的区分列表（键+名称+状态）并请用户选择。
如果没有匹配项，告知用户并建议使用更宽泛的查询内容。

Step 3: Return a Useful Summary

步骤3：返回实用摘要

For a resolved flag, call

get-flag

and return:

Flag key and name
Environment state (
```
on
```
/
```
off
```
)
Off variation and fallthrough behavior
Rule/target complexity (simple vs complex)
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.

对于已解析的标志，调用

get-flag

并返回以下内容：

标志键和名称
环境状态（
```
on
```
/
```
off
```
）
关闭变体和默认行为
规则/目标复杂度（简单或复杂）
标志的直接LaunchDarkly URL（当项目+键已知时）

如果用户询问移除、过时或清理相关问题（例如：“这个可以安全移除吗？”、“我可以清理这个吗？”、“这个过时了吗？”）：

仅显示上述摘要表，然后写入：

此快速查询仅能显示标志的当前配置。若要评估是否可安全移除，你需要使用flag discovery或flag cleanup Skill——它们会扫描代码引用、检查所有环境中的状态并分析下游依赖。

禁止添加结论、项目符号分析、移除步骤、“移除前”检查清单或归档/删除服务。移除相关问题完全由上述路由信息回答。继续执行步骤4。

Step 4: Route to the Right Follow-up Workflow

步骤4：路由到正确的后续工作流

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.

返回摘要后，检查用户的请求是否暗示需要更深层的工作流。如果是，指明对应的Skill并停止操作——不要自行尝试执行该工作流。

用户意图	路由至
创建或修改标志	flag create skill
修改目标受众或发布策略	flag targeting skill
“这个可以安全移除吗？”、“这个过时了吗？”、清理	flag discovery / flag cleanup

对于移除/过时相关的特定问题：遵循上述范围边界说明——仅显示摘要表，然后进行路由。禁止给出结论。

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

/flag

的回复需简洁且具备操作性：

以已解析的标志（或区分列表）开头
仅包含下一步操作所需的最少配置详情
当用户意图不明确时，以一个清晰的下一步问题结尾

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.

```
/flag
```
是一个快速入口，而非完整的生命周期工作流。
当多个标志匹配时，优先选择区分而非猜测。
将项目+环境视为首要上下文；避免隐藏假设。
分享发布百分比时，始终使用易读的百分比格式。
**切勿自行进行移除、过时或清理分析。**始终路由至专用Skill。