跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

configs-create

Create and configure configs in LaunchDarkly. Helps you choose between agent vs completion mode, create the config, add variations with models and prompts, and verify the setup.

launchdarkly · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add launchdarkly/ai-tooling --skill configs-create

技能说明


name: configs-create description: "Create and configure configs in LaunchDarkly. Helps you choose between agent vs completion mode, create the config, add variations with models and prompts, and verify the setup." license: Apache-2.0 compatibility: Requires the remotely hosted LaunchDarkly MCP server metadata: author: launchdarkly version: "1.0.0-experimental"

Create Config

You're using a skill that will guide you through creating a config in LaunchDarkly. Your job is to understand the use case, choose the right mode, create the config and its variations, and verify everything is set up correctly.

⚠️ This skill creates a config — it does not make it servable. A freshly-created config has its fallthrough pointing at an auto-generated disabled variation, not at the variation you just created. The SDK will return ai_config.enabled=False on every evaluation until you flip targeting on and point the fallthrough at your new variation. This is not a bug — it's the default state. You must run /configs-targeting (or the equivalent REST / CLI call shown in Step 5) before verifying against the SDK, or verification will look like the LD-served path is broken when it isn't. The single most common failure mode users hit with this skill is skipping the targeting step and spending time debugging enabled=False in their application code.

Prerequisites

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

Primary MCP tool:

  • setup-ai-config -- create a config with its first variation in one step (recommended)

Alternative MCP tools (for more control):

  • create-ai-config -- create just the config shell (key, name, mode)
  • create-ai-config-variation -- add a variation with model, prompts, and parameters
  • get-ai-config -- verify the config was created correctly

Optional MCP tools (enhance workflow):

  • list-ai-configs -- browse existing configs to understand naming conventions
  • create-project -- create a project if one doesn't exist yet

Important: Bias Towards Action

When the user provides enough context (use case, model, mode), proceed through the entire workflow without stopping to ask for details you can infer. Use reasonable defaults for unspecified fields: default for variation key, the use case as the basis for instructions/messages, kebab-case for config keys. Complete all steps (create + verify) in one pass.

Workflow

Step 1: Understand the Use Case

Before creating, identify what you're building:

  • What framework? LangGraph, LangChain, CrewAI, Strands, OpenAI SDK, Anthropic SDK, custom
  • What does the agent need? Just text generation, or tools/function calling?
  • Agent or completion? See the decision matrix below

Step 2: Choose Agent vs Completion Mode

This choice is about input schema and framework compatibility, not execution behavior. Agent mode returns an instructions string; completion mode returns a messages array. Both provide provider abstraction, A/B testing, and metrics tracking.

Your NeedModeWhy
LangGraph, CrewAI, Strands, AutoGen frameworksAgentFrameworks expect goal/instruction input
Persistent instructions across interactionsAgentSingle instructions string, SDK method: agent_config() (Python) / agentConfig() (Node)
Direct OpenAI/Anthropic API callsCompletionMessages array maps directly to provider APIs
Full control of message structureCompletionSystem/user/assistant role-based messages
One-off text generationCompletionStandard chat format
Need online evaluations (LLM-as-judge)CompletionOnline evals are only available in completion mode

Both modes support tools. Not all models support agent mode -- check model compatibility if using agent mode. If unsure, start with completion mode (it's the API default and more flexible).

Step 3: Create the Config (Recommended: One Step)

Use setup-ai-config to create the config and its first variation in one call. This is the recommended approach: it handles creation, variation setup, and verification automatically.

Config fields:

  • key -- unique identifier (lowercase, hyphens)
  • name -- human-readable name
  • mode -- "agent" or "completion"
  • Optional: description, tags

Variation fields:

  • variationKey, variationName -- identifiers for the first variation
  • modelConfigKey -- must be Provider.model-id format (e.g., OpenAI.gpt-4o, Anthropic.claude-sonnet-4-5)
  • modelName -- the model identifier (e.g., gpt-4o). Always pass this in the initial call — leaving it off produces a variation that displays "NO MODEL" and forces a second PATCH to set it. The field is modelName; it is not name or model.name on this endpoint.

For agent mode, provide:

  • instructions -- a string with the agent's system instructions

Example agent-mode call:

{
  "projectKey": "my-project", "key": "support-agent", "name": "Support Agent",
  "mode": "agent", "variationKey": "default", "variationName": "Default",
  "modelConfigKey": "OpenAI.gpt-4o", "modelName": "gpt-4o",
  "instructions": "You are a customer support agent. Help users resolve their issues."
}

For completion mode, provide:

  • messages -- an array of {role, content} objects (system, user, assistant)

Example completion-mode call:

{
  "projectKey": "my-project", "key": "product-descriptions", "name": "Product Descriptions",
  "mode": "completion", "variationKey": "default", "variationName": "Default",
  "modelConfigKey": "Anthropic.claude-sonnet-4-5", "modelName": "claude-sonnet-4-5",
  "messages": [
    {"role": "system", "content": "You are a product copywriter. Write compelling descriptions."},
    {"role": "user", "content": "Write a description for: {{product_name}}"}
  ]
}

Optional:

  • parameters -- model parameters like `{tempera
阅读完整来源 ↗