CtrlK
BlogDocsLog inGet started
Tessl Logo

mcp-configure

Configure the LaunchDarkly hosted MCP server during onboarding. Use when the parent LaunchDarkly onboarding skill reaches Step 4 (MCP). Supports Cursor, Claude Code, Windsurf, GitHub Copilot, and other MCP-compatible agents. OAuth authentication; no API keys for the hosted server.

75

Quality

92%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured onboarding skill with strong actionability and workflow clarity. The multi-step process includes explicit validation checkpoints, error recovery paths, and migration handling for deprecated configurations. The main weakness is moderate verbosity — some guidance (especially around the quick install link expectations and restart messaging) could be tightened without losing clarity.

Suggestions

Condense the 'what to expect after clicking the link' bullet list in Step 2 into a single concise sentence, e.g., 'After clicking, watch your editor (not the browser) for an approval/add-server prompt; if none appears, check MCP settings or fall back to Step 3.'

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some verbosity that could be tightened — e.g., the lengthy 'tell the user what to expect after clicking the link' guidance in Step 2, the detailed restart messaging in Step 5, and the repeated reminders about not using old servers. Some of this is warranted for a complex onboarding flow, but several paragraphs could be condensed.

2 / 3

Actionability

The skill provides concrete, specific guidance throughout: exact URLs, exact config file paths per agent, specific MCP tool calls to verify (`list-feature-flags`), exact migration steps for deprecated servers, and structured decision points (D-MIGRATE). The instructions are directly executable rather than abstract.

3 / 3

Workflow Clarity

The workflow is clearly sequenced (Steps 1-5) with explicit validation in Step 5 (probe with MCP tool call), a feedback loop for failure (restart → retry → fallback to ldcli/API), and clear error recovery paths. Edge cases are well-handled with blocking decision points and fallback strategies that prevent the workflow from stalling.

3 / 3

Progressive Disclosure

The skill provides a clear overview with well-signaled one-level-deep references to supporting files: MCP Config Templates, MCP UI links, and official docs. Content is appropriately split — the main skill covers the workflow while agent-specific JSON configs and UI navigation details are delegated to reference files.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong, well-crafted description that clearly defines its scope, trigger conditions, and capabilities. It uses third person voice, lists specific supported tools, and provides an explicit 'Use when' clause tied to a concrete trigger (Step 4 of a parent onboarding skill). The description is concise yet comprehensive, making it easy for Claude to select this skill at the right time without ambiguity.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and details: configuring a hosted MCP server, supporting specific agents (Cursor, Claude Code, Windsurf, GitHub Copilot), OAuth authentication, and no API keys. These are specific, actionable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (configure the LaunchDarkly hosted MCP server, OAuth auth, supports multiple agents) and 'when' (use when the parent LaunchDarkly onboarding skill reaches Step 4). The explicit trigger condition is well-defined.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms: 'LaunchDarkly', 'MCP server', 'onboarding', 'Cursor', 'Claude Code', 'Windsurf', 'GitHub Copilot', 'OAuth', 'MCP-compatible agents'. These are terms users and the parent skill would naturally reference.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a very specific niche: it's scoped to LaunchDarkly MCP server configuration during a specific onboarding step (Step 4). This is unlikely to conflict with other skills due to the precise trigger condition and domain.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
launchdarkly/ai-tooling
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.