CtrlK
BlogDocsLog inGet started
Tessl Logo

launchdarkly-experiment-setup

Set up and run experiments in LaunchDarkly. Create experiments with metrics, treatments, and flag config, start iterations to collect data, swap design between iterations, and stop with a winner.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is an exemplary, actionable skill: executable examples, a well-sequenced workflow with a verification checkpoint, and tight, non-redundant prose. Minor duplication of a couple of facts is the only blemish.

DimensionReasoningScore

Conciseness

Lean, task-focused prose with no padding or explanations of basic concepts; every section earns its place, though minor repetition of allocation-sum and 'fallthrough' id exists.

3 / 3

Actionability

Provides fully executable JSON payloads for create, start, evolve, and stop calls plus concrete field lists and named MCP tools — copy-paste ready.

3 / 3

Workflow Clarity

Clear 7-step sequence with an explicit Verify checkpoint (Step 5), a lifecycle map, edge cases, and a 'What NOT to Do' list giving error-recovery guidance.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single file is well-organized into clearly signaled sections, satisfying the simple-skill allowance for progressive disclosure.

3 / 3

Total

12

/

12

Passed

Description

67%

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

The description is specific and well-scoped to a clear niche, but it omits explicit 'Use when' trigger guidance and misses common user phrasings like 'A/B tests' or 'feature flags'. Adding a trigger clause would raise completeness and trigger term quality.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when running A/B tests or experiments in LaunchDarkly, setting up feature-flag experiments, or analyzing experiment results.'

Add common user-facing trigger terms such as 'A/B tests', 'feature flags', and 'experimentation'.

Keep the existing concrete action list; it already grounds the skill well.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Create experiments with metrics, treatments, and flag config', 'start iterations to collect data', 'swap design between iterations', 'stop with a winner'), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers 'what' but lacks any explicit 'when should Claude use it' trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant natural terms ('experiments', 'LaunchDarkly') but omits common variations users would say ('A/B tests', 'feature flags') and lacks any 'Use when...' clause.

2 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (LaunchDarkly experiments) with distinct terminology, making it unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

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.

Validation16 / 16 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.