CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

1.09x
Quality

71%

Does it follow best practices?

Impact

100%

1.09x

1 of 3 eval scenarios. Add 2 more for a full score.

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 content is strong: concrete, tool-specific, and sequenced with an explicit verification step and baseline-safety rules. Its main weaknesses are redundancy between the 'Safety' and 'What NOT to Do' sections and the absence of a full example tool-call payload or explicit error-recovery loop.

Suggestions

Merge 'Safety: Protect the Baseline' and the overlapping 'What NOT to Do' bullets into one section to remove ~6 lines of duplication.

Add one complete example create-agent-config invocation (all required fields plus a single override) to make the clone workflow copy-paste ready.

Add a short recovery path in Step 4 for when verification via get-agent-configs reveals the variation is wrong (e.g., update or delete the failed variation and re-clone).

DimensionReasoningScore

Conciseness

The body is dense with tool-specific knowledge Claude would not know (MCP tool names, field semantics, modelConfigKey format) and avoids explaining general concepts, but it could be tightened: the baseline-protection rules are stated twice ('Safety: Protect the Baseline' and again in 'What NOT to Do' — e.g., 'Do NOT use update-agent-config... on the baseline' vs 'Don't use update-agent-config... to "replace" a baseline'), and the clone-inherits-fields rule from Step 3 is repeated in 'What NOT to Do'. This matches 'mostly efficient but... could be tightened', not 4, which allows only minor trims.

3 / 5

Actionability

Highly concrete for an instruction-only skill: exact tool invocations ('create-agent-config with resource: "variation" and sourceVariationKey'), required fields, per-goal override rules (pass only modelConfigKey/modelName when testing a model), example keys ('gpt4o-mini-cost-test', 'OpenAI.gpt-4o'), and a goal-to-change table. It falls short of 5 only because there is no complete example call payload showing all fields together. It is well above 3, which would mean pseudocode or missing key details.

4 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced with an explicit verification step (Step 4: compare source/created variations, or use get-agent-configs) and reporting requirements. It is not 5 because error recovery is thin — beyond the note about not retrying on partial API responses, there is no explicit validate -> fix -> retry loop for when verification reveals a problem. It clearly exceeds 3, where checkpoints would be missing or only implicit.

4 / 5

Progressive Disclosure

The single-file skill is well organized with clear section headers, a clearly signaled one-level-deep external reference ('read [Create and manage config variations](https://launchdarkly.com/docs/...)'), and related-skill pointers; nothing is buried or nested. It is not 5 because the ~117-line body has some consolidatable content (the duplicated Safety / What NOT to Do material and the modelConfigKey section could be tightened or split), leaving minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

61%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 communicates a clear purpose and decent natural keywords, but it lacks any explicit 'when to use' trigger clause and its action list is generic rather than comprehensive. Adding a 'Use when...' clause with concrete trigger phrases and a fuller enumeration of capabilities would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to experiment with agent configs, A/B test models or prompts, or compare parameter settings.'

Enumerate more concrete capabilities (e.g., clone a baseline variation with selective overrides, verify diffs between variations, keep the baseline safe for rollback) instead of the generic 'creating and managing variations'.

Include natural synonyms users would say, such as 'A/B test', 'optimize', or 'compare models', to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("configs", "variations") and a couple of concrete actions ("creating and managing variations", "test different models, prompts, and parameters"), but the actions are generic and coverage is incomplete — it never mentions measuring/comparing results or the experimentation tooling specifics. It matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor, not 4, which requires several specific listed actions with only minor gaps.

3 / 5

Completeness

The 'what' is clear (create and manage variations to test models, prompts, parameters), but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric guidelines. It is not 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Good natural-term coverage: "configs", "variations", "test different models", "prompts", "parameters", "experiment" are phrases a user would plausibly say when wanting this skill. It falls short of 5 because common synonyms like "A/B test", "optimize", or "try a different model" are missing, but it clearly exceeds the 'some relevant keywords but missing common variations' level of 3.

4 / 5

Distinctiveness Conflict Risk

The experimentation framing ("variations", "systematic experimentation", "test different models") carves out a clear niche distinct from generic config-editing skills, though it overlaps somewhat with closely related sibling skills (configs-create, configs-update) since terms like "configs" are shared. It is mostly distinct with minor overlap risk, above the 'could still overlap with similar skills' level of 3.

4 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

launchdarkly/ai-tooling

Path

skills/agentcontrol/configs-variations/SKILL.md

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.