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

61%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

100%

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

This is a well-crafted deprecation redirect skill. It is maximally concise, clearly communicates the rename, explicitly prevents Claude from executing stale instructions, and directs to the correct replacement. There is nothing to improve for its purpose.

Dimension	Reasoning	Score
Conciseness	The content is extremely lean — it communicates the deprecation, the new skill name, and how to update old references in just a few lines with zero unnecessary explanation.	3 / 3
Actionability	The guidance is concrete and unambiguous: invoke `configs-variations` instead, and update references from `aiconfig-variations` to `configs-variations`. For a redirect/deprecation skill, this is fully actionable.	3 / 3
Workflow Clarity	This is a single-purpose redirect skill with no multi-step process. The single action (use the other skill) is completely unambiguous, and the explicit instruction to not follow any instructions here is a clear safety boundary.	3 / 3
Progressive Disclosure	For a deprecation redirect with no bundle files, the content is appropriately minimal and self-contained. It correctly points to the replacement skill as a single-level reference without unnecessary nesting.	3 / 3
	Total	12 / 12 Passed

Description

22%

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

This is a deprecation redirect stub rather than a functional skill description. While it serves a valid purpose (redirecting old references), it completely lacks capability descriptions, trigger terms, and use-case guidance. As a skill description, it fails to communicate what the underlying skill does or when it should be invoked.

Suggestions

If this skill must exist as a redirect, include a brief summary of what configs-variations actually does (e.g., 'Manages configuration variations for AI configs') so Claude can understand the domain when encountering old references.

Add a 'Use when...' clause that describes the scenarios that should trigger the redirect, e.g., 'Use when the user references aiconfig-variations or asks about configuration variant management, then redirect to configs-variations.'

Include natural trigger terms from the target skill's domain so that if this skill is matched, Claude understands the functional context before redirecting.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions or capabilities. It only states that the skill is deprecated and redirects to another skill name, without describing what the skill actually does.	1 / 3
Completeness	It does not answer 'what does this do' in terms of functionality, nor does it provide 'when should Claude use it' beyond saying to use the other skill instead. Both dimensions are essentially missing.	1 / 3
Trigger Term Quality	It includes the old name 'aiconfig-variations' and the new name 'configs-variations', which serve as redirect keywords. However, there are no natural user-facing trigger terms describing the task domain.	2 / 3
Distinctiveness Conflict Risk	The explicit redirect to 'configs-variations' and mention of the old name 'aiconfig-variations' provides some distinctiveness as a redirect stub, but the lack of any functional description means it could cause confusion about whether to use this or the target skill.	2 / 3
	Total	6 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: launchdarkly/ai-tooling
Commit: 913b745

Reviewed: 10 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.