CtrlK
BlogDocsLog inGet started
Tessl Logo

configs-variations

Experiment with configs by creating and managing variations. Helps you test different models, prompts, and parameters to find what works best through systematic experimentation.

60

10.00x
Quality

62%

Does it follow best practices?

Impact

100%

10.00x

Average score across 1 eval scenario

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/agentcontrol/configs-variations/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

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

The body is a well-structured, actionable guide with a sound workflow and verification steps; its main weaknesses are redundancy between the Safety and What-NOT-to-Do sections and a duplicate Step 3 heading that slightly muddies the sequence.

Suggestions

Collapse the "What NOT to Do" section into "Safety: Protect the Baseline" (or a short checklist) to remove the duplicated guidance.

Fix the duplicate "Step 3" heading by relabeling the alternative path (e.g. "Step 3b: Create from Scratch").

Add one full example MCP tool call showing the complete field set, so the executable guidance is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's knowledge of models/configs, but the "What NOT to Do" section substantially duplicates "Safety: Protect the Baseline" and "Core Principles", and the duplicated "Step 3" numbering adds avoidable noise.

3 / 5

Actionability

Concrete, executable guidance is provided: named MCP tools, required fields (sourceVariationKey, key, name), the modelConfigKey `{Provider}.{model-id}` format, and example identifiers like gpt4o-mini-cost-test; only a full sample tool call is missing.

4 / 5

Workflow Clarity

A clear Step 1–4 sequence with an explicit Verify checkpoint and a "verify via get-ai-config" fallback is present; the duplicate Step 3 numbering and absence of an error-retry feedback loop are minor gaps, and operations are additive (baseline protected) so the destructive cap does not apply.

4 / 5

Progressive Disclosure

A single well-organized SKILL.md with clearly labeled sections and one external docs link, no nested references; at ~104 lines and without bundle files it is well-structured but not a clean 5 since some tool/field reference material could be split out.

4 / 5

Total

15

/

20

Passed

Description

57%Weight 40%Scale 1-5

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 clearly communicates the skill's purpose and domain with reasonable trigger terms, but its second-person voice, missing explicit "Use when…" guidance, and overlap with sibling config skills hold it to a mid-range score.

Suggestions

Rewrite in third person and add an explicit trigger clause, e.g. "Use when the user wants to experiment with AI configs, A/B-test models or prompts, or compare parameter changes."

Sharpen distinctiveness by naming the LaunchDarkly/config-variation context and contrasting with the configs-create and configs-update skills.

DimensionReasoningScore

Specificity

Names concrete actions ("creating and managing variations", "test different models, prompts, and parameters") which would rate a 4, but the second-person voice "Helps you test" triggers the one-point specificity penalty per the rubric.

3 / 5

Completeness

It states a clear "what" (experiment with configs via variations) but lacks any explicit "Use when…" trigger clause, so per the judging guideline completeness is capped at 3 even though the purpose is implied.

3 / 5

Trigger Term Quality

Terms like "configs", "variations", "models, prompts, and parameters", and "experiment" are natural phrases a user would say when A/B-testing a config; a few synonyms (e.g., "A/B testing", "rollouts") are missing, so it sits just below the top anchor.

4 / 5

Distinctiveness Conflict Risk

The experimentation niche is somewhat specific, but "create and manage variations" overlaps materially with the sibling configs-create and configs-update skills referenced in the body, leaving moderate overlap risk.

3 / 5

Total

13

/

20

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.