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.

Quality

64%

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-create/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-executed deprecation redirect skill. It is maximally concise, clearly communicates the rename, directs users to the correct replacement, and provides migration guidance for old references. There is nothing to improve for its intended purpose.

Dimension	Reasoning	Score
Conciseness	The content is extremely lean — it communicates the deprecation, the replacement skill name, and migration guidance in just a few lines with zero unnecessary explanation.	3 / 3
Actionability	The guidance is concrete and unambiguous: invoke `configs-create` instead, and update old references from `aiconfig-create` to `configs-create`. For a redirect 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, which qualifies for a 3 per the simple skills scoring note.	3 / 3
Progressive Disclosure	For a deprecation redirect with no bundle files, the content is appropriately minimal and self-contained. There's no need for external references beyond naming the replacement skill, and the structure is clean.	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 notice rather than a functional skill description. While it serves a valid maintenance purpose by pointing old references to the new skill name, it completely fails as a skill description because it provides no information about capabilities, actions, or trigger conditions. Its only strength is clarity about what NOT to do and distinctiveness in naming.

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 understands the domain when encountering old references.

Add a 'Use when...' clause that explicitly states the redirect condition, e.g., 'Use when the user references aiconfig-create by name; immediately redirect to configs-create skill instead.'

Include natural trigger terms from the actual functionality (e.g., 'config', 'configuration', 'AI config') so Claude can properly route even if users use the old name in a natural language context.

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 a 'when should Claude use it' clause. The only guidance is to NOT use this skill and use another 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%

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.