CtrlK
BlogDocsLog inGet started
Tessl Logo

aiconfig-create

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

57

Quality

64%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/agentcontrol/aiconfig-create/SKILL.md
SKILL.md
Quality
Evals
Security

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 actionable, and appropriately structured for its single purpose of redirecting users to the renamed `configs-create` skill. There is nothing to improve given its intentionally narrow scope.

DimensionReasoningScore

Conciseness

The content is extremely lean — it communicates the deprecation, the replacement 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-create` instead, and update references from `aiconfig-create` to `configs-create`. For a redirect/deprecation skill, this is fully actionable.

3 / 3

Workflow Clarity

For a single-purpose deprecation redirect, the workflow is trivially clear: do not use this skill, use the named replacement. No multi-step process or validation is needed, and the single action is unambiguous.

3 / 3

Progressive Disclosure

The content is appropriately minimal for a redirect skill. It points to exactly one destination (`configs-create`) with no unnecessary nesting or inline content that belongs elsewhere.

3 / 3

Total

12

/

12

Passed

Description

29%

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 effectively communicates that Claude should not use this skill and should invoke 'configs-create' instead, it completely lacks any description of capabilities, actions, or trigger conditions. Its only strength is distinctiveness due to the explicit naming of both old and new skill identifiers.

Suggestions

If this skill must exist as a redirect, add a brief summary of what configs-create does (e.g., 'Creates AI configuration files') so Claude can still match user intent if the old name is referenced.

Add a 'Use when...' clause such as 'Use when the user references aiconfig-create by name; immediately redirect to configs-create' to provide explicit trigger guidance.

Include natural trigger terms related to the underlying functionality (e.g., 'AI config', 'configuration creation') so Claude can route correctly even without the exact skill name.

DimensionReasoningScore

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 either skill actually does.

1 / 3

Completeness

It does not answer 'what does this do' in terms of functionality, nor does it provide a 'when should Claude use it' clause. The only guidance is to not use this skill and to invoke another one instead.

1 / 3

Trigger Term Quality

It includes the old name 'aiconfig-create' and the new name 'configs-create', which serve as redirect trigger terms. However, it lacks any natural user-facing keywords describing the actual task domain.

2 / 3

Distinctiveness Conflict Risk

The description is very clear about its purpose as a deprecated redirect, explicitly naming both the old ('aiconfig-create') and new ('configs-create') skill names, making it unlikely to conflict with unrelated skills.

3 / 3

Total

7

/

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.

Validation11 / 11 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.