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.

60

Quality

75%

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

96%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 a model deprecation stub: minimal, unambiguous, and immediately actionable, telling the reader both what not to do and exactly where to go. Its only imperfection is cosmetic — a flat structure with no sections, which barely matters at five lines.

DimensionReasoningScore

Conciseness

Five lean lines with no padding and no explanation of concepts Claude already knows — every token earns its place in delivering the redirect.

5 / 5

Actionability

The instruction is fully executable: "Invoke the `tools` skill instead" plus a concrete remediation step ("update it from `aiconfig-tools` to `tools`") with no ambiguity about what to do.

5 / 5

Workflow Clarity

A single, unambiguous action with an explicit guard ("Do not follow any instructions here"); the simple-skill exception applies and there are no destructive or batch operations requiring validation.

5 / 5

Progressive Disclosure

The pointer to the `tools` skill is well-signaled and exactly one level deep, which is the right structure for a stub; the only minor gap is the flat paragraph layout with no sectional organization, though none is strictly needed at this size.

4 / 5

Total

19

/

20

Passed

Description

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

As a deprecation stub, the description communicates its redirect purpose clearly and unambiguously, but it scores poorly on capability specificity and natural trigger terms because it intentionally describes no capabilities. The absent "when to use" clause is the main structural weakness under this rubric.

Suggestions

Add a brief capability summary of the renamed skill (e.g., what 'tools' covers) so the description conveys what the user is being redirected to, improving specificity.

Include natural trigger terms users would actually say (the task keywords the original skill handled) so old prompts mentioning those needs still route correctly.

Add an explicit 'Use when...' style clause — e.g., 'Use only when an old reference names aiconfig-tools' — to make the invocation condition explicit.

DimensionReasoningScore

Specificity

The description names its purpose ("DEPRECATED redirect — this skill was renamed to tools") but the only actions stated are "invoke tools instead" and "point users to the new name" — minimal and generic rather than a list of concrete domain capabilities.

2 / 5

Completeness

It has a clear "what" (a deprecation redirect to the tools skill) but no "Use when..." trigger guidance at all, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Keywords are meta-terminology ("DEPRECATED", "redirect", "renamed", "aiconfig-tools", "tools") rather than natural phrases a user would say when they need the skill's functionality; only one or two generic terms are present.

2 / 5

Distinctiveness Conflict Risk

It occupies a very distinct niche (an alias for one specifically named skill) and explicitly says "Do not use this skill", leaving only minor overlap risk from the generic target name "tools".

4 / 5

Total

11

/

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.

Validation — 16 / 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.