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.

82

2.75x
Quality

72%

Does it follow best practices?

Impact

99%

2.75x

Average score across 3 eval scenarios

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

85%Weight 40%Scale 1-3

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

The content is highly actionable with a clearly sequenced, validated workflow and strong safety guardrails, well-suited to a single-file instruction skill. Its main weakness is mild redundancy across the principles, safety, and anti-pattern sections.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, using compact tables and direct instructions, but the guidance is repeated across 'Core Principles', 'Safety: Protect the Baseline', and 'What NOT to Do', which could be tightened.

2 / 3

Actionability

Provides concrete tool names, explicit required fields, precise override-only instructions with field-level examples, and a modelConfigKey format — fully actionable, copy-ready guidance for an instruction-only MCP skill.

3 / 3

Workflow Clarity

A clear four-step sequenced workflow includes an explicit verify step and a feedback loop ('Note on API responses' addressing retry/verify behavior), with safety guardrails for destructive baseline operations.

3 / 3

Progressive Disclosure

A single well-organized SKILL.md under ~100 lines with clearly headed sections and no need for external bundle files; per the simple-skills note this warrants a 3.

3 / 3

Total

11

/

12

Passed

Description

60%Weight 40%Scale 1-3

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 conveys what the skill does with concrete actions but omits an explicit 'when to use' trigger clause, capping its completeness. Trigger terms are relevant but lean technical rather than mirroring natural user phrasing.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when experimenting with AI configs, A/B testing models, prompts, or parameters') to lift completeness and trigger-term coverage.

Include natural user phrasings like 'A/B testing', 'experiment', or 'compare models' alongside the technical terms.

Tie the description more tightly to the LaunchDarkly/config-variation niche to reduce overlap with generic config skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'creating and managing variations' and 'test different models, prompts, and parameters' — matching the anchor for naming several specific actions.

3 / 3

Completeness

The 'what' is clearly stated but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Relevant keywords like 'configs', 'variations', 'models', 'prompts', and 'parameters' are present but somewhat technical and miss common natural phrasings such as 'A/B testing' or 'experiment' that a user might say.

2 / 3

Distinctiveness Conflict Risk

The configs/variations niche is fairly specific but 'configs' alone is generic enough to potentially overlap with adjacent configuration skills, so it does not reach the clear-distinctive-niche anchor.

2 / 3

Total

9

/

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.