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

68%

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

92%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 content is a model of brevity and clarity for a deprecated-redirect skill: it states what changed, what to do instead, and how to fix stale references without any wasted tokens.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no padding or over-explanation; every line earns its place by stating the rename, the action to take, and how to update stale references.

5 / 5

Actionability

It gives concrete, executable direction ('Invoke the tools skill instead', 'update it from aiconfig-tools to tools') with only minor gaps; it is not a 5 because it lacks an explicit example of a corrected invocation.

4 / 5

Workflow Clarity

As a simple single-purpose instruction skill, the one action (invoke tools, update references) is unambiguous and fully sequenced, satisfying the simple-skill exception; no destructive or batch operation requires validation.

5 / 5

Progressive Disclosure

The body is under 50 lines, well-organized with a clear header, and needs no external references, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

19

/

20

Passed

Description

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

This is a well-formed deprecation/redirect description that is unambiguous about its purpose and deliberately minimizes misuse, though it naturally lacks capability actions and natural trigger terms because it is not a functional skill.

Suggestions

If kept long-term, consider adding a brief note on where to find replacement capability keywords so migrated users have a positive trigger path, not only a 'do not use' directive.

Ensure the 'tools' replacement description (in the target skill) carries the natural trigger terms and capability actions that this redirect omits.

DimensionReasoningScore

Specificity

The description names the domain (a deprecated redirect/rename) but lists no concrete capability actions, matching 'Names the domain but actions are minimal or generic'; it is not a 3 because no concrete actions are enumerated.

2 / 5

Completeness

It clearly states what the skill is ('DEPRECATED redirect — renamed to tools') and explicitly addresses when to use it (do not use; invoke tools instead), but the 'when' is a negative instruction rather than a positive trigger, which caps it at the midpoint.

3 / 5

Trigger Term Quality

It contains only technical identifiers ('aiconfig-tools', 'tools') and no natural phrases a user would say to invoke a capability, sitting just above the 'no natural keywords' anchor but well short of meaningful coverage.

2 / 5

Distinctiveness Conflict Risk

It occupies a clear, unambiguous niche as a redirect and actively discourages its own invocation, so it is highly distinguishable with minimal conflict risk.

5 / 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.