aiconfig-variations

DEPRECATED redirect — this skill was renamed to configs-variations. Do not use this skill; invoke configs-variations instead. Kept only so old references to aiconfig-variations still point users to the new name.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/agentcontrol/aiconfig-variations/SKILL.md

Quality

Content

100%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 body is an exemplary lean redirect: brief, actionable, and well-organized with no extraneous context. It fully serves its single purpose of pointing users to configs-variations.

Dimension	Reasoning	Score
Conciseness	Every line earns its place: a heading, a do-not-use directive, the replacement skill, and a note for stale references, with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	Gives concrete, executable guidance — 'Invoke the configs-variations skill instead' and 'update it from aiconfig-variations to configs-variations' — with nothing missing for a redirect.	3 / 3
Workflow Clarity	A simple single-purpose skill whose one action (redirect to configs-variations, plus update stale references) is unambiguous and clearly sequenced; no validation checkpoints are needed.	3 / 3
Progressive Disclosure	Under 50 lines with no need for external references and well-organized sections (heading + short paragraphs), satisfying the simple-skill allowance for progressive disclosure.	3 / 3
	Total	12 / 12 Passed

Description

35%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 is an explicit, honest deprecation redirect but is not a capability description: it lacks natural trigger terms and a positive 'Use when...' clause. It scores moderately because it communicates its redirect purpose clearly while serving no functional trigger role.

Suggestions

Add natural trigger terms users would actually say (e.g., 'config variations', 'variant configs') so the redirect is discoverable beyond the internal skill name.

Include an explicit trigger framing such as 'Use when a reference asks for aiconfig-variations; redirect to configs-variations' to satisfy the 'when' half of completeness.

Tighten the conflict-risk phrasing by stating the redirect is only for legacy references, reinforcing that new invocations should go directly to configs-variations.

Dimension	Reasoning	Score
Specificity	Names a concrete domain (configs-variations) and concrete redirect actions ('invoke configs-variations instead', 'update it from aiconfig-variations to configs-variations'), but describes no functional capabilities of the skill itself, so it is not comprehensive.	2 / 3
Completeness	It clearly states what the skill is (a deprecated redirect) but provides no positive 'Use when...' trigger guidance; the 'when' is only implied (do not use), which caps completeness at 2.	2 / 3
Trigger Term Quality	The phrasing is deprecation/administrative jargon ('DEPRECATED redirect', 'renamed', 'old references') with no natural capability keywords a user would say to find this skill's function.	1 / 3
Distinctiveness Conflict Risk	It is clearly named and explicitly redirects, but by design overlaps with the real configs-variations skill, so old references still trigger this deprecated entry instead.	2 / 3
	Total	7 / 12 Passed

Validation

100%

Warnings & errors only

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/aiconfig-variations/SKILL.md
Commit: e6ab09b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.