CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

100%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 an exemplary deprecated-redirect stub: concise, immediately actionable, and clearly structured, directing the reader to the replacement skill and telling maintainers to update stale references. No bundle files exist and none are needed, which fits its single-purpose role.

DimensionReasoningScore

Conciseness

The body is a lean four-line redirect notice with zero padding and no explanation of concepts Claude already knows; every token earns its place. It assumes Claude's competence by simply stating the rename and the corrective action.

5 / 5

Actionability

As an instruction-only skill the guidance is fully actionable: 'Invoke the configs-variations skill instead' is a concrete executable action, and 'update it from aiconfig-variations to configs-variations' gives a specific remediation. The rubric notes absence of code is not penalized in instruction-only skills when guidance is actionable, which holds here.

5 / 5

Workflow Clarity

This is a single-purpose redirect with one unambiguous action (invoke the replacement skill), so the simple-skill exception applies and workflow clarity scores 5. No destructive or batch operations are involved, so the validation-cap rule does not apply.

5 / 5

Progressive Disclosure

The content is under 50 lines, needs no external bundle files (none are present), and is organized with a clear heading and short paragraphs, satisfying the simple-skills exception. Its single one-level-deep pointer to configs-variations is clearly signaled rather than buried.

5 / 5

Total

20

/

20

Passed

Description

46%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 is clear and honest about its deprecated-redirect purpose, with concrete redirect actions and specific skill identifiers that keep conflict risk low. Its main weakness is the absence of natural trigger terms and an explicit 'Use when...' clause, which leaves the 'when' only weakly implied.

Suggestions

Add an explicit trigger clause such as 'Use when an old reference or saved prompt invokes aiconfig-variations, so you can redirect to configs-variations' to lift completeness past 3.

Include a natural-language phrase a user might actually say (e.g. 'AI config variations' or 'aiconfig variations') alongside the technical identifier to improve trigger-term quality.

Briefly state the redirect's effect ('returns no actions itself; forwards invocation to configs-variations') to round out the concrete action list and push specificity toward 4.

DimensionReasoningScore

Specificity

The description names the domain ('DEPRECATED redirect') and a couple concrete actions ('invoke configs-variations instead', 'point users to the new name'), but coverage is narrow rather than comprehensive. It does not reach 4 because only one or two concrete actions are stated and they are all about the redirect mechanics, not a broader capability set.

3 / 5

Completeness

It clearly answers 'what' (a deprecated redirect stub kept for backward-compatible references) but only weakly implies 'when' via 'Kept only so old references to aiconfig-variations still point users to the new name', with no explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

The keywords present are the technical skill identifiers 'aiconfig-variations' and 'configs-variations' rather than natural phrases a user would actually say when needing this skill. It is above 1 because those identifiers can serve as triggers for old references, but it lacks the natural user vocabulary that would push it to 3 or higher.

2 / 5

Distinctiveness Conflict Risk

Naming both the old ('aiconfig-variations') and new ('configs-variations') skill identifiers gives it a distinct, tightly-scoped niche with minimal conflict risk. It does not reach 5 because the description describes a redirect role rather than a clear functional trigger phrase that distinguishes it from sibling skills.

4 / 5

Total

12

/

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.