CtrlK
BlogDocsLog inGet started
Tessl Logo

aiconfig-tools

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

67

Quality

80%

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-tools/SKILL.md
SKILL.md
Quality
Evals
Security

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.

An exemplary minimal redirect body: concise, fully actionable, and clearly organized with no wasted tokens. It does exactly what a deprecation stub should and nothing more.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanation of concepts Claude already knows; every line serves the redirect purpose.

3 / 3

Actionability

It gives concrete, executable guidance: 'Invoke the `tools` skill instead' and 'update it from `aiconfig-tools` to `tools`', leaving no ambiguity about what to do.

3 / 3

Workflow Clarity

As a simple single-action redirect skill, the one required action (invoke tools) is unambiguous and explicitly stated, which the simple-skill scoring note allows to score 3.

3 / 3

Progressive Disclosure

The skill is well under 50 lines, needs no external references, and is organized with a clear heading and short paragraphs, satisfying the simple-skill progressive-disclosure criterion.

3 / 3

Total

12

/

12

Passed

Description

60%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.

A clear, concise deprecation redirect that names the replacement skill and migration action, but it is thin on natural trigger terms and an explicit 'Use when' clause. Its inherent overlap with the successor 'tools' skill also limits distinctiveness.

Suggestions

Add an explicit trigger clause such as 'Use when an old reference still points to aiconfig-tools' to satisfy the 'when should Claude use it' requirement and raise completeness.

Include natural user-facing terms (e.g., 'aiconfig tools', 'AI config') alongside the technical 'DEPRECATED redirect' phrasing to improve trigger-term quality.

Clarify that this skill must never perform work itself and should only forward to 'tools', to reduce conflict risk between the two similarly named skills.

DimensionReasoningScore

Specificity

The description lists concrete redirect actions — 'invoke tools instead' and 'update it from aiconfig-tools to tools' — rather than vague language.

3 / 3

Completeness

It states what the skill does (redirect to tools) and a partial when ('old references to aiconfig-tools'), but lacks an explicit 'Use when...' trigger clause, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

It surfaces 'tools' and 'aiconfig-tools' but leans on technical/structural terms ('DEPRECATED redirect', 'renamed') rather than natural phrases a user would say to trigger the skill.

2 / 3

Distinctiveness Conflict Risk

The redirect name 'aiconfig-tools' intentionally overlaps with the target 'tools' skill, so it could trigger alongside or instead of the real skill in ambiguous cases.

2 / 3

Total

9

/

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.

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.