CtrlK
BlogDocsLog inGet started
Tessl Logo

aiconfig-custom-metrics

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

56

Quality

62%

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

Quality

Content

76%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 clean, lean deprecated-redirect notice that does exactly what it should: stop the reader and point to the replacement skill, plus tell maintainers to update old references. It loses only minor points for the slight duplication of the redirect instruction and the absence of an example invocation.

Suggestions

De-duplicate the redirect instruction between the heading and first line to tighten conciseness toward a 5.

Add a one-line example invocation of the replacement custom-metrics skill to nudge actionability to a 5.

DimensionReasoningScore

Conciseness

The body is short and assumes Claude's intelligence ('Do not follow any instructions here', 'invoke custom-metrics instead') with no padded explanation of what a skill rename is, matching the score-4 anchor of efficient content with minor over-explanation. The near-duplication of the redirect instruction between the heading and the first line keeps it just below a 5.

4 / 5

Actionability

It gives concrete, executable direction ('Invoke the custom-metrics skill instead') and a concrete remediation ('update it from aiconfig-custom-metrics to custom-metrics'), matching the score-4 anchor of mostly-executable guidance. It is not score 5 because there is no copy-paste command or example invocation, and not score 3 because the instruction is specific rather than a high-level hint.

4 / 5

Workflow Clarity

The single action (redirect to custom-metrics, optionally update the old reference) is unambiguous and correctly ordered, so under the simple-skill exception it can score above 3; the instruction to stop, switch skills, and update references is clear, matching score 4. It is not score 5 because there is no explicit validation/checkpoint confirming the caller reached the right skill, but the simple redirect needs none.

4 / 5

Progressive Disclosure

This is a short skill (well under 50 lines) with no bundle files and no need for external references; per the scoring notes, progressive disclosure can score 5 with just well-organized sections, and the body is cleanly split into a heading and two short paragraphs. There are no nested references or inlined content that belongs elsewhere.

5 / 5

Total

17

/

20

Passed

Description

48%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 deprecated-redirect description that clearly states its purpose and points to the replacement skill. It caps at completeness 3 because it lacks an explicit 'Use when...' trigger clause, and specificity is limited since a redirect has few concrete actions to describe.

Suggestions

Add an explicit trigger clause such as 'Use when an old prompt, doc, or automation references aiconfig-custom-metrics' to lift completeness above 3.

Expand trigger-term coverage with natural synonyms callers might use (e.g. 'AI config metrics', 'custom metrics skill') to improve trigger_term_quality.

DimensionReasoningScore

Specificity

Quotes 'redirect — this skill was renamed to custom-metrics' and 'Kept only so old references to aiconfig-custom-metrics still point users to the new name'; it names the concrete domain (a deprecated redirect pointing to custom-metrics) but lists only minimal generic actions rather than multiple specific capabilities, matching the score-2 anchor of naming a domain with minimal actions. It does not reach score 3 because there are not 1-2 concrete operational actions beyond 'invoke custom-metrics instead'.

2 / 5

Completeness

It clearly answers 'what' (a deprecated redirect kept for old references) but the 'when' guidance is only weakly implied via 'Kept only so old references... still point users'; per the judging guideline a missing explicit 'Use when...' clause caps completeness at 3. It is not score 4 because no explicit trigger clause is present, and not score 2 because the 'what' is stated clearly.

3 / 5

Trigger Term Quality

Contains the natural keywords a user or reference would mention ('aiconfig-custom-metrics', 'custom-metrics', 'old reference') but lacks broader synonyms or file-extension variations, matching the score-3 anchor of 'some relevant keywords but missing common variations'. It is above score 2 because the exact skill names a caller would type are present, and below score 4 because coverage is limited to the two skill names with no surrounding natural phrasing.

3 / 5

Distinctiveness Conflict Risk

The two distinct skill names 'aiconfig-custom-metrics' and 'custom-metrics' make it clearly distinguishable and unlikely to trigger for the wrong skill, matching the score-4 anchor of 'mostly distinct; minor overlap risk'. It is not score 5 because the language does not add concrete trigger phrases beyond the names, and not score 3 because the names alone provide a clear niche.

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